apidom
apidom copied to clipboard
swagger-api
Semantic parser for API specifications
Following implementation of JSON Schema namespaces, this ticket is about updating apidom-ls to support standalone JSON Schema fiiles, involving rules, parser selection, and possibly other areas
The goal of this epic is to have JSON Schema and their various drafts and versions as separate ApiDOM namespace. Here is the list of specification we want to support...
Following binding objects do have nested objects for their fixed fields. These nested objects are currently not easily identifiable by `element` or `class`. In order to provide remediation for this...
As specification extensions are technically patterned fields, we must validate them as such.
When Binding Objects schema contains Schema Object as one of it's properties, sometimes it must follow following rules: - schema MUST be of type object - schema MUST have a...
For schemas (all JSON Schema-likes), we have the `required` field that declares some of the properties as being required. While autosuggest works for this (hooray!) and we get validation warning...
This is to add rules (validation and autosuggestion) for message.examples in AsyncAPI (2.x) Eg: ```yml channels: pets.added: description: The topic for newly added Pets. publish: message: examples: - #
### Is your feature request related to a problem? The validation error of "Object includes not allowed field" does not tell me which field isn't allowed. I'd like it to...