Ted Epstein
Ted Epstein
Discussed in [support ticket #176](https://support.reprezen.com/helpdesk/tickets/176) In that context, the Swagger.io editor caught a logical problem in the schema definition that SwagEdit did not catch: a schema had property listed in...
Reported by @andylowry: Seen in current master build of API Studio: Open a Swagger or OAS3 model file in SwagEdit. Make any change, and the "dirty" indicator (an asterisk) appears...
This is an untested fix for #418. As noted by @tfesenko , we need to assess performance impact on large files before merging.
One of our users reported a problem shown in swagger-editor, but not reported in KZOE: > *Semantic error at paths./offers/{offerId}* > Declared path parameter "offerId" needs to be defined as...
(Backlog issue, not important right now.) We (mostly) solved this for the RAPID-ML editor. (See [ZEN-3861](https://modelsolv.atlassian.net/browse/ZEN-3861)) We would like this same behavior for the quick outline view in the OpenAPI...
The additionalProperties allowed in many of the Swagger and JSON Schema objects can be useful, but can also lead to subtle bugs. It's easy to have properties that you assume...
Noted here: https://modelsolv.atlassian.net/browse/ZEN-3421?focusedCommentId=43532&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-43532 The validation error marker, and therefore the quick fix, only show for top-level schema objects. An array of objects with a missing type:object in the sub-schema will...
When editing OpenAPI 3.0, I can see schema templates wherever a subschema is allowed. At least, I have confirmed that this works with a property subschema:  It _should_ also...
This is another way to improve the validation error message for oneOf schema validations: #60 contains an example of a Swagger spec with a `oneOf` schema violation, and also includes...