Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Mention HyperFuel for wildcard indexing #552

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Mention HyperFuel for wildcard indexing #552

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f9817d4
Mention HyperFuel for wildcard
DZakh Dec 4, 2024
b90771e
Fixes
DZakh Dec 5, 2024
7c88f40
Revert formatting changes
DZakh Dec 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/HyperIndex/Advanced/wildcard-indexing.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Wildcard indexing is a feature that allows you to index all events matching a sp

:::note
Wildcard Indexing is only supported from HyperIndex v2.3 onwards.
Wildcard Indexing is supported for Indexers using [HyperSync](/docs/HyperIndex/Advanced/hypersync.md) as data source.
Wildcard Indexing is supported for Indexers using [HyperSync](/docs/HyperIndex/Advanced/hypersync.md) or [HyperFuel](/docs/HyperIndex/fuel/fuel.md) as data source.
Wildcard indexing is not yet supported for Indexer using [RPC](/docs/HyperIndex/Advanced/rpc-sync.md) as data source.
:::

Expand Down
5 changes: 4 additions & 1 deletion docs/HyperIndex/Guides/event-handlers.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ in the project directory to generate the functions you will use in your handlers
Each event that you want to process requires that a handler be registered. These functions are asynchronous.

**Note:** _Two other functions, `handlerWithLoader` and `contractRegister`, are also sometimes used but not required for most indexers. Both functions are explored in the Advanced section. `handlerWithLoader` is used to optimize the loading of entities from the database, and accessing one-to-many relationships on entities, `contractRegister` is used for registering addresses dynamically from a factory contract._

<!-- TODO: add links to the advanced section about handlerWithLoader and contractRegister -->

## Handler Function
Expand Down Expand Up @@ -119,7 +120,7 @@ type BlockFields = {
} & AdditionalBlockFields;
```

It is recommended to add `# yaml-language-server: $schema=../../codegenerator/cli/npm/envio/evm.schema.json` to the top of your `config.yaml` to help with editor autocompletion.
It is recommended to add `# yaml-language-server: $schema=./node_modules/envio/evm.schema.json` to the top of your `config.yaml` to help with editor autocompletion.

### Context

Expand Down Expand Up @@ -257,7 +258,9 @@ Handlers.Greeter.NewGreeting.handler(async ({ event, context }) => {
Maybe this "Config data in the handler" section shouldn't be included here.
It is a more advanced topic and can be covered in its section.
-->

## Config Data in the Handler

We expose the `config.yaml` data in the handler via `getConfigByChainId`. The below code snippets show how to access the `config.yaml` data in the handler and the available data:

<Tabs>
Expand Down