fix(plugin): Fix nullable enum not having a proper enum type #2553
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently when having a nullable enum
SomeEnum | null
, the generated output from the plugin is missing theenum
attribute. It looks like this in the unit test:This would further down the line crash the application start with this error:
swagger/lib/services/schema-object-factory.ts
Lines 330 to 332 in 6555285
My usual workaround was to manually annotate these cases, however, I implemented a fix with this PR for the plugin.
What is the new behavior?
With this fix, the generated output look as expected:
Does this PR introduce a breaking change?
Other information