Skip to content

Strict typing not enforced by default? #120

@Riffz

Description

@Riffz

I've created a JSON schema and I'm trying to verify that a few fields are strings. However if they have other values like true, 42, or null they are converted to a string and the schema validates the json as correct. On your wiki you say that your validator should be using jackson while enforcing strict typing. Is this still the case, or is it possible to force this behavior? For reference, here is my schema.

I've been using sample output from a JIRA server and I currently want to validate the keys in the schema and I'm not worried about the other keys. If need be I could try to trim this ~10kb of text down to something more manageable or I could put it on gist.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions