You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When importing a component, Bit normally checks whether there are changes to the component and throw an error if they are.
However, when a dependency is imported to the workspace and a user is now importing its dependent it overrides the dependency although it has changed.
Steps to Reproduce
create two components compA => compB, whereas compA requires compB.
import compB and change it.
import compA.
Notice how compB has been overridden.
Expected Behavior
In case the dependency has changed, it should throw an error saying it can't import the component due to the change.
Also, change the error message to include a suggestion of using --merge flag, as follows: unable to import the following components due to local changes, use --merge flag to merge your local changes or use --override flag to override them.
Describe the bug
When importing a component, Bit normally checks whether there are changes to the component and throw an error if they are.
However, when a dependency is imported to the workspace and a user is now importing its dependent it overrides the dependency although it has changed.
Steps to Reproduce
Notice how compB has been overridden.
Expected Behavior
In case the dependency has changed, it should throw an error saying it can't import the component due to the change.
Also, change the error message to include a suggestion of using
--merge
flag, as follows:unable to import the following components due to local changes, use --merge flag to merge your local changes or use --override flag to override them
.Specifications
CC: @itaymendel
The text was updated successfully, but these errors were encountered: