graphprotocol
[Feature] Declarative Call Enforcement
Description
We have run into some declarative calls failing. In our mappings we utilize the try_{ethCall} in order to get things like token.name, token.symbol, token.decimals however in rare circumstances contracts will not have this functionality. Rather than failing the subgraph I would prefer that declarative calls simple try to make the eth call.
Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.
No response
Some information to help us out
- [ ] Tick this box if you plan on implementing this feature yourself.
- [x] I have searched the issue tracker to make sure this issue is not a duplicate.
Would you be able to provide some logs with the error. I tried to reproduce this issue by setting decalrative calls to a non erc-20 contract (hardcoded address in the manifest file) and calling the same contract from the mapping with try_. In my case I would get a 0x response from the rpc (infura/alchemy), that will result in a decoding error and the call being marked as reverted.
