Skip to content
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

improvement(scope-rename), support renaming exported components #8456

Merged
merged 10 commits into from
Jan 26, 2024

Conversation

davidfirst
Copy link
Member

@davidfirst davidfirst commented Jan 25, 2024

Currently, bit scope rename supports only new components. For exported, it suggests users to run bit rename one by one, which can be an hassle.
This PR combines the logic from "rename", "renameScope" and "renameOwner" to one place "renameMultiple" and allows renaming multiple components, some can be exported, some can be new.
Previously, some of the actions during the rename were done only on "rename" or only on "renameScope", now all of them are aligned.

@davidfirst davidfirst merged commit 0465ce2 into master Jan 26, 2024
11 checks passed
@davidfirst davidfirst deleted the support-rename-scope-exported branch January 26, 2024 18:26
davidfirst added a commit that referenced this pull request Jan 30, 2024
This is a regression caused by #8456.
When renaming a component with a namespace it was emitting the
namespace, which resulted in ComponentNotFound error.
Also, it was loading the components after the rename before changing
their env in case the env was renamed as well.
Both issues are fixed in this PR.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants