Skip to content

Saving = Remote Saving in ESC Explorer can be too much sometimes #16

@ZacHigi

Description

@ZacHigi

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

When saving a change to an ESC environment it immediately posts the changes and versions up to ESC. This is reasonable but is a break from the more typical git-based workflows a lot of us use in the IDE. It would be nice to save locally, and then 'push' changes to the remote ESC environment when ready.

Save early, save often, is muscle memory for many engineers, and the act of saving doesn't necessarily translate to saving remotely even after understanding it is a remote save. In an extreme case, we had an engineer using an auto-save extension in their vscode install, and when combined with the ESC plugin generated 100's of unwanted revisions to an ESC environment.

Affected area/feature

ESC Explorer

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/escRelated to ESC functionality.kind/enhancementImprovements or new features

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions