-
-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nullable does not work ? #33
Comments
Maybe the JSON schema version of |
The editor does not complain with But it shouldn't work as per the specification:
|
Hi @ymarillet! Sorry for the late response. I'm currently on holidays and can't help so much but there are two issues here:
Would you mind creating a PR on https://github.com/asyncapi/docgen? |
Hello there I don't have much time to work on this unfortunately :(, but will try to as soon as I get some spare time.. In the meantime, please do not consider I'm working on it activly. I really like the project though, hope it'll get even better ! |
Could these help?
I'd love a solution to this issue too! Also, since AsyncAPI isn't OpenAPI why not just use a subset of JSON Schema Draft XY? OpenAPI schemas are not exactly a subset + history has shown people get confused between the two + there are way more JSON Schema validators/tools than there are for OpenAPI Schemas... I can't wait for both these standards to support "here's my schema in language XYZ" :) |
@fenollp I'm glad you ask for multiple schema support. It's already implemented in the spec for version 2.0.0, which should be ready by May this year. Check it out: |
@fmvilas Nice! May isn’t far off too :) |
We removed support for multiple formats on a single message for simplicity of the spec because that's not the case of many people. Overlays will allow you to do that. In any case, if the message is not exactly the same, they should be different messages. |
This was fixed by #204. Closing. |
As defined in the specification, any Schema Object MAY have a "nullable" property, but I can't make it working in the editor, nor find it in the spec implementation (https://github.com/asyncapi/asyncapi/blob/master/schema/asyncapi.json)
Should it be removed from the doc ?
The text was updated successfully, but these errors were encountered: