-
-
Notifications
You must be signed in to change notification settings - Fork 288
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
Add support for using $ref and local files at any place in the asyncapi file #937
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
Additional related issue: #778 |
Related to #868 |
Adding my use case to this one - we have one team who maintains a lot of separate APIs, and so there's many common elements between the different asyncapi docs that have to be duplicated (or pre-processed separately) without this functionality. Things like team contacts, reusable components like the server security scheme, etc. |
Related to asyncapi/parser-js#797 - adding my use case too. this feature is essential for us, when describing large apis |
Adding my use case to this |
Similar issue to #778 |
Closing in favour of #778 |
Maintaining one big asyncapi-file with markdown, examples etc. is a major headache when it starts to grow. We have a lot of apis and developers who make frequent changes, and this causes a lot of additional work.
Please consider adding support for $ref (or another tag) to include local external files at any place in the structure, to improve maintainability.
Also see issue:
asyncapi/generator#963
The text was updated successfully, but these errors were encountered: