jsonsystems / public

122 stars 6 forks source link

Error when adding `exclusiveMaximum` property #42

Closed FlavioCurella-minted closed 1 year ago

FlavioCurella-minted commented 1 year ago

Could this be a typo in KEYWORD_EXCLUSIVE_MAXIUMUM?

{
    "headers": {
        "normalizedNames": {},
        "lazyUpdate": null
    },
    "status": 400,
    "statusText": "OK",
    "url": "https://api.jsonschema.net/v1/graphs/204928/nodes/133975870:editJson?key=AIzaSyCFCGe0Ypcl1WjJkCLa6kFQiRX7aaLx-N8",
    "ok": false,
    "name": "HttpErrorResponse",
    "message": "Http failure response for https://api.jsonschema.net/v1/graphs/204928/nodes/133975870:editJson?key=AIzaSyCFCGe0Ypcl1WjJkCLa6kFQiRX7aaLx-N8: 400 OK",
    "error": {
        "message": "keyword: invalid value \"KEYWORD_EXCLUSIVE_MAXIUMUM\" for type type.googleapis.com/jsonschema.v1.Keyword",
        "code": 400
    }
}
jackwootton commented 1 year ago

Thanks for reporting the issue, and for the recommended fix. You were spot on. A fix has been deployed to www.jsonschema.net.

FlavioCurella-minted commented 1 year ago

Thank you!