QuantConnect/lean-cli

Standardize Handling of Conflicting Project Names to Local Platform Behavior

Opened this issue · 0 comments

  • 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