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: hugo/content/docs/recipes/scoping/file-based.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,11 +58,11 @@ npm run langium:generate
58
58
59
59
## Step 2: Exporting persons to the global scope
60
60
61
-
The index manager shall get all persons that are marked with the export keyword. In Langium this is done by overriding the `ScopeComputation.getExports(…)` function. Here is the implementation:
61
+
The index manager shall get all persons that are marked with the export keyword. In Langium this is done by overriding the `ScopeComputation.collectExportedSymbols(…)` function. Here is the implementation:
Next, we can start implementing our custom scoping by overriding the `computeExports` function. This function is particularly important, as it allows us to change export nodes of our model using qualified names: We'll also want to annotate this function with `override`, since there's already a default definition provided.
52
+
Next, we can start implementing our custom scoping by overriding the `collectExportedSymbols` function. This function is particularly important, as it allows us to change export nodes of our model using qualified names: We'll also want to annotate this function with `override`, since there's already a default definition provided.
0 commit comments