@anotherfullstack
First, regarding the GQL that Ponder provides. It is cool, really cool but lacks some important features what probably detracts users from using it. What additional GQL features I would love to have when working on a project with Ponder:
- Add an additional field to the GQL Object Type + perform sorting and filtering based on this field. Real work use-case might be a total number of transactions per user and select the top 5 users by the number of transactions;
- Write custom queries that have connection to other object types. For instance I want to somehow specially select ERC20 transfers and for that I want to write a custom resolver, but also I want to resolve other entities that are related to the transfer (transaction data for instance) without explicitly doing that in the resolver (by utilizing the way how GQL resolvers do cascade work);
- Write "where" conditions for parent objects based on child objects;
0 reply
0 recast
0 reaction