-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
[typescript-angular] Fix inner enum reference in multi-map property type #22748
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
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
b112c18
[typescript-angular] Fix inner enum reference in multi-map property type
saxicek decf2cf
[typescript] Fix inner enum reference in multi-map property type
saxicek 94499fa
test for the double-prefixed enum names
saxicek 8f72be1
Implement review comment about the trailing `>`
saxicek 213ee3f
fix @type for generic interfaces in TypeScript clients
saxicek File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P2: Inner enum names can be double-prefixed for child properties when a model has a parent: processCodegenProperty already prefixes isInnerEnum, and the new inheritance loop prefixes isInnerEnum again on cm.allVars, which reuses the same property objects for child vars.
Prompt for AI agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The concern about double-prefixing is theoretical but not an actual bug in practice. My investigation shows:
Why there's no double-prefix bug:
For TypeScriptFetch:
cm.parentis always null because TypeScriptFetchClientCodegen does NOT setsupportsMultipleInheritance = true. The entireif (cm.parent != null)block is dead code.For generators that DO support inheritance (typescript-angular, etc.): When
supportsMultipleInheritance = true, thecm.allVarscollection contains COPIES of the properties, not references to the same object instances ascm.vars.Therefore, modifying properties in
cm.varsdoes not affect the (different) property objects incm.allVars. Added commit 94499fa as a proof.