invalid json shoud be rejected

[evantill]

invalid json data should be rejected

invalid content (config_vars must be inside engine_args)

{
    "engine": "tesseract",
    "engine_args": {
        "lang": "fra",
        "psm": "3"
    },
      "config_vars": {
        "tessedit_create_hocr": "1",
        "tessedit_pageseg_mode": "1"
    },
    "img_url": "http://i.imgur.com/xYAaDjV.png"
}

[tleyden]

@evantill yup, agree 100%, thanks for pointing this out.

There's only one problem: the json schema is currently embedded in an apiary.apib file, and so it's not easy to pass that to a json schema validation library.

They're working on it in apiaryio/api-blueprint#20

[angrbrd]

@tleyden just curious if the issue of rejecting an invalid JSON payload has ever been re-evaluated? Will this ever be addressed? At this time, an invalid payload to the mock server produces a message in the Apiary inspector log, but the request still goes through and returns a response. Thanks!

[tleyden]

Hi @angrbrd. Sorry, no progress or ETA on this yet, but I'll make sure to update the issue.

On this note, what would your thoughts be about moving from apiary to swagger? As a user would you prefer one over the other?

[angrbrd]

@tleyden I do tend to prefer Swagger and it seems that it has grown in popularity and garnered enough support to have a larger user base now, as apposed to apiary (at least that's my personal impression). But there is always a transition period, that's the issue. We have a lot of Apiary blueprints that have yet to be converted over to Swagger, which is what is driving this exploration. Thanks for any help with this.