-
-
Notifications
You must be signed in to change notification settings - Fork 262
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
Guidelines on anyOf #58
Comments
Hey @SensibleWood! Yes, that's currently not supported by mistake. I'm already fixing it for version 2.0.0, which will be out very soon. Thanks for pointing out! Will update whenever it gets fixed. |
Nice one thanks @fmvilas - attempting to use Async API in anger in some projects I'm working on - it's great work, thanks very much for the effort you've put into it |
Thanks @SensibleWood! Really appreciate 😊 |
Will be fixed in v1.1.0. Make sure it also covers the problem described at #38. |
🎉 This issue has been resolved in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
When I attempt to include
anyOf
in Async API editor a schema definition I get the following:[ { "code": "OBJECT_ADDITIONAL_PROPERTIES", "params": [ [ "anyOf" ] ], "message": "Additional properties not allowed: anyOf", "path": "#/components/schemas/DirectDebit/allOf/1", "schemaId": "http://asyncapi.hitchhq.com/v1/schema.json#", "description": "A deterministic version of a JSON Schema object." } ]
However I can't see anywhere in the documentation that says
anyOf
is specifically excluded.Please can you clarify where anyOf is supported or not? Thanks.
The text was updated successfully, but these errors were encountered: