Skip to content

fix: Explicitly use strings for boolean-named enums #413

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: Explicitly use strings for boolean-named enums #413

wants to merge 1 commit into from

Conversation

@zaakn
Copy link

@zaakn zaakn commented Nov 9, 2023

use yaml type tag !!str to represent boolean-like and NULL enum values.

fixes: #407

@zaakn
fix: Explicitly use strings for boolean-named enums
2d36742 
use yaml type tag `!!str` to represent boolean-like and `NULL` enum values.

fixes: google#407
@zaakn zaakn requested a review from a team as a code owner November 9, 2023 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

protoc-gen-openapi: Enum types that use stringified boolean values like "TRUE" are treated as the real boolean values

1 participant

@zaakn