fix(compiler-cli): do not error due to multiple components named equally#54273
Closed
devversion wants to merge 2 commits intoangular:mainfrom
Closed
fix(compiler-cli): do not error due to multiple components named equally#54273devversion wants to merge 2 commits intoangular:mainfrom
devversion wants to merge 2 commits intoangular:mainfrom
Conversation
Currently, when two components are named `TestComponent`, and both would use e.g. control flow. Templates would be generated by the compiler and those would conflict at runtime because the names for the template functions are not ensured to be unique. This seems like a more general problem that could be tackled in the future in the template pipeline by always using the `ConstantPool`, but for now, we should be good already, given us ensuring the `baseName`'s are always unique.
crisbeto
approved these changes
Feb 6, 2024
JoostK
approved these changes
Feb 6, 2024
…ed equally Fix test diff for i18n
jessicajaniuk
pushed a commit
that referenced
this pull request
Feb 6, 2024
…lly (#54273) Currently, when two components are named `TestComponent`, and both would use e.g. control flow. Templates would be generated by the compiler and those would conflict at runtime because the names for the template functions are not ensured to be unique. This seems like a more general problem that could be tackled in the future in the template pipeline by always using the `ConstantPool`, but for now, we should be good already, given us ensuring the `baseName`'s are always unique. PR Close #54273
Contributor
|
This PR was merged into the repository by commit bfbb306. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
Currently, when two components are named
TestComponent, and both would usee.g. control flow. Templates would be generated by the compiler and those would
conflict at runtime because the names for the template functions are not ensured to be unique.
This seems like a more general problem that could be tackled in the future in the
template pipeline by always using the
ConstantPool, but for now, we should begood already, given us ensuring the
baseName's are always unique.