This repository was archived by the owner on Feb 17, 2024. It is now read-only.
Update raml-10.md #769
Open
Update raml-10.md #769
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Making the declaration of the annotation type optional. This will allow better interoperability with OAS, where extensions are not required to have a strict schema. This also makes it possible to easily generate annotations when enriching the spec via software for automation use cases. The change is backward compatible. Users that want to provide a better experience can still provide the annotation type.
|
Git2Gus App is installed but the |
Adding more details to the explanation of how annotations can be used without declaration
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Making the declaration of the annotation type optional.
This will allow better interoperability with OAS, where extensions are not required to have a strict schema.
This also makes it possible to easily generate annotations when enriching the spec via software for automation use cases.
The change is backward compatible. Users that want to provide a better experience can still provide the annotation type.