-
Notifications
You must be signed in to change notification settings - Fork 182
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
Mark service.version as stable. #106
Mark service.version as stable. #106
Conversation
Co-authored-by: Christian Neumüller <[email protected]>
Co-authored-by: Armin Ruech <[email protected]>
FYI, our latest change clarifies that version can technically be any string, as defined by the owner, etc. |
type: string | ||
brief: > | ||
The version string of the service API or implementation. The format is not defined by these conventions. | ||
examples: ["2.0.0"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please manually apply the markdown suggestion also to the YAML (NB: re-running the genererator will revert @arminru's suggestion; I advise to suggest preferably in the YAML to avoid accidental reverts)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, thank you!
type: string | ||
brief: > | ||
The version string of the service API or implementation. The format is not defined by these conventions. | ||
examples: ["2.0.0"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, thank you!
Reopening this from the related Specification PR.
cc @jsuereth