Description
Currently, if a user attempts to push a component with the same name under the same category, we display an error message indicating that the component already exists in this category. Instead, provide an option to override the previous component if the user wants to replace it.
Potential solution
A new flag, like --override or -o, which will update the component with the new one. Also, show this option when we show the error message that the component already exists.
- The backend needs to be modified to override the component when a new parameter like
override is set to true
Additional context
- If the user uses
-o or --override , then the component should be replaced. Also, inform them about this option when showing the error message.
Description
Currently, if a user attempts to push a component with the same name under the same category, we display an error message indicating that the component already exists in this category. Instead, provide an option to override the previous component if the user wants to replace it.
Potential solution
A new flag, like
--overrideor-o, which will update the component with the new one. Also, show this option when we show the error message that the component already exists.overrideis set totrueAdditional context
-oor--override, then the component should be replaced. Also, inform them about this option when showing the error message.