Remove the internal prefix for value fields #647
Merged
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.
📒 Description
The originalCase convention performs no string transformations when used for field/classes/... names.
The generator is also using the field name
@value
for all infered text nodes.These two don't work very well together.
Resolves #646
🔗 What I've Done
In the past enumeration classes were allowed to be inner|nested. To resolve that issue I used the prefix @ for value fields in order to quickly identify these cases when the generator had to copy inner classes from one class to another.
It's being a while now that all enumeration classes are promoted to root classes, so that hack to identify these cases is no longer necessary so it's safe to remove that part of the code and also remove the @ prefix that is causing the issue #646
💬 Comments
Hopefully most of these hacks from the early days are long gone.
🛫 Checklist