alexjoybc
alexjoybc
any update on fixing this? I understand the ux challenge, but it would be nice be able to access the hooks test output in the livedoc report
I would like to help for sure, we are evaluating using vss for one of our project and having jsonschema available would be a good starting point for us.
Yes I agree, jsonschema should be generated through tooling without impacting the current JSON definition and not impact the yaml core definition. JsonSchema has greater adoption by the web community...
find bellow an example of using vss jsonschema with open api v3: ```json { "openapi": "3.0.1", "info": { "title": "VSS with open api", "description": "", "version": "1.0.0" }, "paths": {...
Just seeing this now... I will have a look next week thanks for the feedback
Is there any update on this issue? we are facing the same problem where we have to return different objects depending on the status of the response....