-
Notifications
You must be signed in to change notification settings - Fork 32
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
Some keyword escaping happens in the wrong places #1441
Comments
I think you are running into #1398 There was a reason why I alsso added the escaping to the enum but can't remember why. I'll take a look. Maybe a PR for upstream is easier. |
I've made a PR upstream. |
Yep, looks like your PR will fix it. |
This still happens. With the example above it is not necessary to add the dollar sign because it is in the middle of the name, so we shouldn't do it to keep it more readable. |
At least the code is now correctly generated after your upstream fix. |
So this is now only cosmetic? |
Only cosmetic, but it also is a breaking change (see the PR). |
Type
must be added as a keyword to avoid collisions.I quickly tried adding it, but then generating leads to these errors:
I believe this is generating bad code where
Type
is now also escaped inside the name:@Leptopoda do you mind taking a look? This is breaking the update to the latest specs :/
The text was updated successfully, but these errors were encountered: