We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
given we handle a lot of Open API specification given the fact that license are mostly always the same
it would be great that $ref being supported for the field license
this feature is not a breaking change could be added either to moonwalk project or beeing a feature candidate for 3.2.X
following this pattern
license: $ref: ../_shared/license.yaml
this would requires a change in the meta schema
notice that even if license support url , the use case is not really the same...
should be handle the same way as #3552
The text was updated successfully, but these errors were encountered:
Consolidating under #3853 and closing
Sorry, something went wrong.
No branches or pull requests
given we handle a lot of Open API specification
given the fact that license are mostly always the same
it would be great that $ref being supported for the field license
this feature is not a breaking change could be added either to moonwalk project or beeing a feature candidate for 3.2.X
following this pattern
license:
$ref: ../_shared/license.yaml
this would requires a change in the meta schema
notice that even if license support url , the use case is not really the same...
should be handle the same way as #3552
The text was updated successfully, but these errors were encountered: