Using "encoding/json.Validate" as a field validator | CUE

Jonathan Matthews

This Commented CUE demonstrates how to use the built-in function encoding/json.Validate as a field validator.

It asserts that properly-formed JSON, encoded in a string, adheres to specific constraints by checking that the data and schema unify successfully.

package example

import "encoding/json"

data: """
	{
	  "a": 1,
	  "b": "two"
	}
	"""

// Validate requires only that data adheres to schema constraints.
// Missing fields do not cause validation failures.
data: json.Validate(_outOfBoundsSchema)
data: json.Validate(_missingFieldSchema)

_outOfBoundsSchema: {
	a!: >99 // validation failure
	b!: string
}
_missingFieldSchema: {
	a!: int
	b!: string
	c!: bool // NOT a validation failure
}

$ cue vet
data: invalid value "{\n  \"a\": 1,\n  \"b\": \"two\"\n}" (does not satisfy encoding/json.Validate({a!:>99,b!:string})): error in call to encoding/json.Validate: invalid value 1 (out of bound >99):
    ./file.cue:14:7
    ./file.cue:5:7
    ./file.cue:15:7
    ./file.cue:18:6
    json.Validate:2:8

encoding/json.Validate validates JSON data that is encoded in a string.

To validate data stored in a separate .json file, use CUE’s native and simpler unification instead.
This is documented in validating JSON with CUE

How-to Guide: Using "encoding/yaml.Validate" and "encoding/yaml.ValidatePartial" as field validators
The encoding/json built-in package

Related content