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

Standardize Handling of Conflicting Project Names to Local Platform Behavior #374

Open
rjra2611 opened this issue Oct 17, 2023 · 0 comments

Comments

@rjra2611
Copy link
Member

  • Project config corruption causes the CLI to lose track of the project cloud id and create a duplicate with project name 2

  • CLI Current Behavior:

    • on pull: Finds alternate name on conflict and pulls to the new directory. Also, updates the name in the cloud
    • on push: Renames locally on conflict/corruption and also renames in the cloud
  • Local Platform's current behavior

    • on pull: Fail and warn on conflict
    • on push: does not have any native logic for this case but maybe can be the same as pul i.e fail
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

No branches or pull requests

1 participant