support having multiple components with the same name but different scope-name in the same workspace #7897
Conversation
This file contains 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
…cope-name in the same workspace
…to support-same-name
…to support-same-name
…to support-same-name
…to support-same-name
…ifferent versions, keep the latest
…ot collide with other same-name comps
…to support-same-name
…to support-same-name
…to support-same-name
GiladShoham
approved these changes
Oct 2, 2023
This was referenced Dec 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR removes the restriction Bit always had of having components with the same-name but different scope-name in one workspace.
For now, the case of multiple new components with the same-name is not supported. They need to be exported.
Also, because it's experimental, it's disabled by default. To enable it, use the bit-feature of
allow-same-name.