We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There should be a single wasm module which contains multiple functions, 1 per event. The fn name may follow the pattern index_<event_name>.
index_<event_name>
E.g.
#[indexer(manifest = "<path/to/file/escrow.manifest.yaml>")] mod escrow_index { fn index_accepted_arbiter_event(event: AcceptedArbiterEvent, block: BlockData) { ... } fn index_created_escrow_event(event: CreatedEscrowEvent, block: BlockData) { ... } // more events below }
Each type in graphql should have a required field and use the @indexed directive to allow for easier querying.
required
@indexed
From the BlockData we should retrieve the block height and add it to each event so that we have a measure of time for when the event took place.
BlockData
The indexer should be implemented for the following apps: [ ] - Escrow [ ] - AMM [ ] - Multisig [ ] - English Auction [ ] - Airdrop
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Indexer Guideline
There should be a single wasm module which contains multiple functions, 1 per event. The fn name may follow the pattern
index_<event_name>
.E.g.
Each type in graphql should have a
required
field and use the@indexed
directive to allow for easier querying.From the
BlockData
we should retrieve the block height and add it to each event so that we have a measure of time for when the event took place.The indexer should be implemented for the following apps:
[ ] - Escrow
[ ] - AMM
[ ] - Multisig
[ ] - English Auction
[ ] - Airdrop
The text was updated successfully, but these errors were encountered: