tree abc2c463bed9db08ee5fa164490feab5e8148f5b
parent c174a086fdf920ebcf4e88bf2d1ec15065141fdd
author Marcel van Lohuizen <mpvl@golang.org> 1588783438 +0200
committer Marcel van Lohuizen <mpvl@google.com> 1589388443 +0000

encoding/jsonschema: use new definition mapping

This allows JSON Schema to now directly be compared to
data without qualifiers or remapping:

   $ cue eval schema.json data.yaml

This works now more intuively as data and schema now map
one-to-one.

This relies on the change to allow `...` at the file level. This means
it is not necessary to use the new `isSchema` field. It seems
sensible to track this though and we may need it in the future.

One huge caveat of this new mapping is that it is now no longer
possible to have a non-struct schema with definitions remapped
to a different label. For this we need to allow embedded scalars in
structs. It still seems worth it and rather to allow this in the language.

Change-Id: I16988ca1c0d4436d591ba239964c4bb7445e6fd9
Reviewed-on: https://cue-review.googlesource.com/c/cue/+/5942
Reviewed-by: Marcel van Lohuizen <mpvl@google.com>