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: website/src/pages/en/subgraphs/guides/subgraph-linter.mdx
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,13 +11,12 @@ It complements existing tools by helping you catch problems locally while writin
11
11
12
12
Run Subgraph Linter when you want to detect handler and mapping issues that don't often appear until indexing starts, such as:
13
13
14
-
- Entities are saved with missing required fields
15
-
- Multiple instances of the same entity handled at the same time causing overwrite issues
16
-
- Optional values are force-unwrapped without checks
17
-
- Divisions happen without proving the divisor is non-zero
18
-
- Derived fields are mutated directly or left stale
19
-
- Contract calls are made without being declared in the manifest
20
-
14
+
- Entities saved with missing required fields
15
+
- Entity overwrite issues from concurrent/stale instances
16
+
- Optional values force-unwrapped without checks
17
+
- Divisions without guaranteeing a non-zero denominator
18
+
-`@derivedFrom` fields mutated directly or left stale
19
+
- Contract calls are used without being declared in the manifest
21
20
These bugs usually compile fine, but crash at runtime or silently produce incorrect data. Subgraph Linter performs static analysis on your mapping code to detect these issues before deploying the subgraph.
0 commit comments