Document apiVersion 0.0.7, specVersion 0.0.5 and receipts in mappings

[tilacog]

This PR briefly documents the changes introduced in graphprotocol/graph-node#3373.

I'm not sure if those changes are enough for it to be considered to be final, so I'll be happy to refine this PR based on the team's suggestions.

The feature PR linked above contains lots of extra detail if more context is needed.

[evaporei]

Just warning for the reviewers, this shouldn't be merged until this is in the Hosted Service, for now it's only on the master branch of graph-node.

[azf20]

Thanks @tilacog @evaporei! Just a ping to make sure we remember to merge this when the above are deployed

[azf20]

LGTM, excited for this one!

[tuler]

Is there a performance penalty of defining receipt: true?

[azf20]

hey @tuler it requires an additional RPC call, so there will be an impact, but we have not yet got metrics for that

[ammanpashasc]

Hey, is this available yet for the hosted service?

[azf20]

Hey @ammanpashasc yes it is, are you having trouble with it?

[ammanpashasc]

Hey @ammanpashasc yes it is, are you having trouble with it?

Hey, yeah so I've upgraded to graph-cli@0.29.2 and also updated the specVersion to 0.0.5 and apiVersion to 0.0.7. But when I try to add the receipt: true to event mapping, it gives me error:

Path: dataSources > 0 > mapping > eventHandlers > 0
Unexpected key in map: receipt 

This is what my .yaml file looks like:

   - kind: ethereum/contract
    ......
      eventHandlers:
        - event: Assign(indexed address,uint256)
          handler: handleAssign
          receipt: true
      file: ./src/mappings/mapping.ts

Any idea what I'm doing wrong?

---

Edit: nvm, my bad. Had to upgrade the packages to graph-ts@0.27.0-alpha.1 and graph-cli@0.30.0-alpha.1