Fix visibility for enum in C# generator#21984
Merged
wing328 merged 1 commit intoOpenAPITools:masterfrom Sep 18, 2025
ferenc-a:patch-1
Merged
Fix visibility for enum in C# generator#21984wing328 merged 1 commit intoOpenAPITools:masterfrom ferenc-a:patch-1
wing328 merged 1 commit intoOpenAPITools:masterfrom
ferenc-a:patch-1
Conversation
Member
|
thanks for the pr let's give it a try i'll add a test later |
Member
|
FYI. Merged #21996 to add a test for |
rajvesh
pushed a commit
to rajvesh/openapi-generator
that referenced
this pull request
Dec 25, 2025
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.
The visibility of enums in the C# generator is wrong, and results in build errors with
nonPublicApi=true.Here are sanitized build error logs before the fix:
A slightly related issue I found that seems resolved now: #11357.
PR checklist
Read the contribution guidelines.
Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
Run the following to build the project and update samples: - I'd kindly ask an active contributor of this project to do this.
(For Windows users, please run the script in WSL)
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
File the PR against the correct branch:
master(upcoming7.x.0minor release - breaking changes with fallbacks),8.0.x(breaking changes without fallbacks)If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having
"fixes #123"present in the PR description)If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.