2a09582fa4
A dynamic reference is like a dynamic variable in a programming language, with two twists: - There must be a dynamic anchor in lexical scope for the ref to resolve. (Think of it as declaring the dynamic variable.) - The ref resolves to the schema highest on the stack, not lowest. That feels odd, but it turns out to work for the intended purpose, which is to provide extension points for additional features. There is some distracting code motion and refactoring in this CL: resolveRefs was moved down in the file, and resolution of a single ref was split off. Change-Id: I17da6052e0782fc540d14b8a41b06a2645923872 Reviewed-on: https://go-review.googlesource.com/c/tools/+/674155 Auto-Submit: Jonathan Amsterdam <jba@google.com> Reviewed-by: Alan Donovan <adonovan@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
21 lines
637 B
JSON
21 lines
637 B
JSON
[
|
|
{
|
|
"description": "validate definition against metaschema",
|
|
"schema": {
|
|
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
|
"$ref": "https://json-schema.org/draft/2020-12/schema"
|
|
},
|
|
"tests": [
|
|
{
|
|
"description": "valid definition schema",
|
|
"data": {"$defs": {"foo": {"type": "integer"}}},
|
|
"valid": true
|
|
},
|
|
{
|
|
"description": "invalid definition schema",
|
|
"data": {"$defs": {"foo": {"type": 1}}},
|
|
"valid": false
|
|
}
|
|
]
|
|
}
|
|
]
|