We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cue version
v0.11.0-alpha.5
No, although it might have related issues. v0.10.0 version of encoding/jsonschema doesn't use matchN.
matchN
exec cue def -o schema.cue jsonschema: schema.json exec cat schema.cue exec cue vet schema.cue data.json -- schema.json -- { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "matchN": { "oneOf": [{ "type": "string", "pattern": "^foo" }, { "type": "boolean" }] } } } -- data.json -- {"matchN": false}
Passing test.
> exec cue def -o schema.cue jsonschema: schema.json > exec cat schema.cue [stdout] @jsonschema(schema="https://json-schema.org/draft/2020-12/schema") matchN?: matchN(1, [=~"^foo", bool]) ... > exec cue vet schema.cue data.json [stderr] matchN: cannot call non-function matchN (type bool): ./schema.cue:2:10 [exit status 1] FAIL: /tmp/z.txtar:3: unexpected command failure
Note: this does not happen when using cue import: in that case, the matchN field is quoted correctly.
cue import
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What version of CUE are you using (
cue version
)?Does this issue reproduce with the latest stable release?
No, although it might have related issues.
v0.10.0 version of encoding/jsonschema doesn't use
matchN
.What did you do?
What did you expect to see?
Passing test.
What did you see instead?
Note: this does not happen when using
cue import
: in that case, thematchN
field is quoted correctly.The text was updated successfully, but these errors were encountered: