Skip to content

[FEAT] Override option when pushing a component whose name already exists. #58

@Shreehari-Acharya

Description

@Shreehari-Acharya

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

Image
  • If the user uses -o or --override , then the component should be replaced. Also, inform them about this option when showing the error message.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backendAPI, Database, Server taskscliCommand Line Interface specific tasksenhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions