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: README.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,6 +147,12 @@ validate:
147
147
- references # checks that references resolve, either locally or in the remote API
148
148
# or
149
149
# methods: "*"
150
+
references:
151
+
selector:
152
+
- studentAssessments.studentReference
153
+
- studentSchoolAssociations.schoolReference
154
+
behavior: exclude # or `include`
155
+
remote: False # default=True
150
156
```
151
157
Default `validate`.`methods` are `["schema", "descriptors", "uniqueness"]` (not `references`; see below). In addition to the above methods, `lighteam validate` will also (first) check that each payload is valid JSON.
152
158
@@ -167,6 +173,8 @@ This is optional; if absent, references in every payload are checked, no matter
167
173
* `fetch`ed data becoming stale over time
168
174
* needing to track which data is your own vs. was `fetch`ed (all the data must coexist in the `config.data_dir` to be discoverable by `lightbeam validate`)
169
175
176
+
You may specify a `selector` list of the form `someEndpoint.path.to.someReference` to include or exclude (according to `behavior`) specific references from reference validation. You may also specity `remote: False` to only validate references against local data in your JSONL files.
self.logger.error(f"`config.validate.references.selector` {selector} is incorrectly formatted (should be `someEndpoint.someReference`, such as `studentSchoolAssociation.schoolReference`)")
0 commit comments