fix: Pascal case enum names in exports block #966
+2
−1
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 of changes
A PR was added removing pascal casing for some enum definitions.
One of the places where pascal casing was actually ADDED is JS models'
index.jsfile that defines enums, then exports them.However, in the
exportblock, the pascal casing transformation wasn't applied, leading to a potential mismatch between names.E.g:
(enum) MyCTA => MyCtatransformation generated aMyCtaenum but was trying to exportMyCTACodegen Paramaters Changed or Added
None
Issue #, if available
None
Checklist
yarn testpassespath) behave differently on windows.type,input,enum,interface,unionand scalar types.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.