Enum generation descriptions - allow for nulls/empty strings #2393
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.
Changes
Expands the condition for skipping enum descriptions to also ignore null and empty strings.
Details
Since NSwag.AspNetCore v14.5, it seems that a descriptions array is always generated for enums, with null values for any undefined entries. This appears to be intended to maintain positional alignment with enum values, and there’s no built-in way to override it due to being a private field. This change ensures such null or empty entries are not appended.
I can't see anything in the spec that would suggest that null is an invalid value for a description but at the moment you get a null reference exception:
How to Review
Give it an openapi spec like this and check that the process runs to completion with no errors and that no descriptions are generated.
Checklist
docs/
updated (if necessary)pnpm run update:examples
run (only applicable for openapi-typescript)