Add details on enums in OpenAPI section #33995
Merged
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
mikekistler
commented
Nov 4, 2024
captainsafia
reviewed
Nov 4, 2024
captainsafia
approved these changes
Nov 4, 2024
Member
captainsafia
left a comment
captainsafia
left a comment
There was a problem hiding this comment.
One comment about more examples here. LGTM otherwise.
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.
This PR adds just a bit more detail about enum metadata to the OpenAPI section of the docs. Specifically, it adds an example of the JsonConverter attribute and explains how flag enums are handled (and why).
Internal previews