You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Good timing, apparently the issue that was blocking us from doing dynamic data sources is fixed graphprotocol/graph-node#892 .
I haven't looked into it deeply, but from what I interpret, we can now get null returned instead of the graph node crashing. This should allow us to handle all contracts dynamically. This will also allow us to make token, decimals, and name all required in schema.graphql (Noah did this in his PR but I just noticed we didn't add it in Ians PR)
@ianlapham take a look at this, let me know if you have any questions. If you can implement it that would be amazing! This week I am busy but I can get to it next week. If you need help reach out on discord.
The text was updated successfully, but these errors were encountered:
Good timing, apparently the issue that was blocking us from doing dynamic data sources is fixed graphprotocol/graph-node#892 .
I haven't looked into it deeply, but from what I interpret, we can now get
null
returned instead of the graph node crashing. This should allow us to handle all contracts dynamically. This will also allow us to make token, decimals, and name all required inschema.graphql
(Noah did this in his PR but I just noticed we didn't add it in Ians PR)@ianlapham take a look at this, let me know if you have any questions. If you can implement it that would be amazing! This week I am busy but I can get to it next week. If you need help reach out on discord.
The text was updated successfully, but these errors were encountered: