Allow to annotate class constants as properties#1193
Merged
Conversation
6b74504 to
1848e63
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thanks to @cdaguerre for the idea and initial work; replaces #1147.
related to Is annotation of class constants supported in v4? #1082)
constkeyword to attributesconstto a single valueenumfor OAS 3.0.01. Attributes on class constants
2. Support the
constkeyword in attributesThis ^^code is equivalent to the example above in terms of generated documentation.
3. Backport
consttype properties for versions < 3.1The
constkeyword was introduced in OAS 3.1, eg.In OAS < 3.1, the recommended way of doing this was to declare a single-valued enum instead, eg.