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
Tools such as json-schema exist for validating that json meets a predefined schema.
Any provided model to core should be validated against a schema.
Given golang seems only to have a json-schema validator, perhaps core should aim to work only with JSON. Or convert yaml to JSON in order to validate it like that.
The text was updated successfully, but these errors were encountered:
I'm actually less keen on this. With UnmarshalStrict we do a bit of schema checking already. This issue would just guard against extra unused fields being present.
That would be better. But not as useful as I originally thought.
Tools such as json-schema exist for validating that json meets a predefined schema.
Any provided model to core should be validated against a schema.
Given golang seems only to have a json-schema validator, perhaps core should aim to work only with JSON. Or convert yaml to JSON in order to validate it like that.
The text was updated successfully, but these errors were encountered: