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
Copy file name to clipboardExpand all lines: docs/subgraph-manifest.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,6 +64,7 @@ The `mapping` field may be one of the following supported mapping manifests:
64
64
| --- | --- | --- |
65
65
|**event**|*String*| An identifier for an event that will be handled in the mapping script. For Ethereum contracts, this must be the full event signature to distinguish from events that may share the same name. No alias types can be used. For example, uint will not work, uint256 must be used.|
66
66
|**handler**|*String*| The name of an exported function in the mapping script that should handle the specified event. |
67
+
|**topic0**| optional *String*| A `0x` prefixed hex string. If provided, logs whose topic 0 is equal to this value will be processed by the given handler. By default, this is equal to the hash of the event signature. This is useful for processing solidity anonymous events. |
67
68
68
69
## 1.6 Path
69
70
A path has one field `path`, which either refers to a path of a file on the local dev machine or an [IPLD link](https://github.com/ipld/specs/).
0 commit comments