feat: add optional configuration parameter to generate native Typescript enums #1058
Conversation
This file contains 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
melloware
requested changes
Nov 19, 2023
|
Thanks letting the build run now! |
melloware
approved these changes
Nov 20, 2023
|
@melloware Hi, please tell, when you will make a release with these changes? very necessary) |
|
@anymaniax handles releases I pinged him. |
|
@DiRover 6.21.0 is out if you want to try this now. |
|
@melloware thx! It works! |
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.
Status
READY
Description
Fix #907
As requested in issue #907 this PR adds a new optional configuration parameter to generate native Typescript enums.
The new parameter
useNativeEnumsis set in theoutput.overrideconfiguration block and when set totrue(defaults tofalse) Orval will generate a native Typescriptenuminstead of thetypeandconstcombo.