-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
replace spaces with underscores in (enum) identifiers #46
Comments
ok - i wonder if pure number enums would cause issues as well. |
try using 5.7 |
great! This solves that issue. Unfortunately there are still a few more problems, I will open new issues |
I've decided that this seems to be the best available null-safe code generator out there, so I'll invest some more time to analyse what all the errors are that I run into, and will be posting a |
Sounds good to me!
…On Tue, Jun 15, 2021, 11:08 PM NANASHI0X74 ***@***.***> wrote:
I've decided that this seems to be the best available null-safe code
generator available, so I'll invest some more time to analyse what all the
errors are that I run into, and will be posting a slew of issues describing
them if that's ok :p
When I've identified all the issues I can try and help fix them myself as
well
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#46 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAANTWGKYGCVIKTNH7BCFBDTS4YC5ANCNFSM46VTS2ZQ>
.
|
Hi, I've just ran into a problem trying out this generator (switching from one of the openapi-generator-cli default ones). Our Api defines an enum with a bunch of languages and some of the names of these languages contain spaces. The generated code then contains enum definitions where individual enum values contain spaces , for example
dart sees these as two seperate identifiers without a comma in between, which is invalid. One way to fix this may be to replace spaces with underscores in the enum value identifiers.
The relevant part of my spec looks something like this:
The text was updated successfully, but these errors were encountered: