feat: Extend useEnums to all schema files #223
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.
Problem
The useEnum flag currently only generates the enums for the types defined in the schemas section of the OpenApi file.
If you define an enum directly in the parameter section, string literals are still used to define the type.
Solution
Using the same logic from the schema enum generator, the enums can also be generated for responses, requestBodies and parameters.
Limitation
This only covers the enums generated for the types generated by
generateSchemaTypes
. The components file will still generate string literals for parameters. This can be seen for the tests withcolorParam
in generatingReactQueryComponents.test.ts.