search

forcedotcom / code-builder-feedback

This repository is used to collect feedback for the Code Builder beta.
29 stars 2 forks source link

Not sure about automatic save functionality #130

Closed randi274 closed 2 years ago

randi274 commented 2 years ago

General feedback In the desktop extensions, it's common to enable push on save and also detect conflicts on sync. However, when I did this, it was constantly throwing conflict errors since it was trying to deploy before I was ready. I'd like to be able to be able to choose whether or not to have save automatically enforced when I make fail changes, but also be able to use push on save.

gbockus-sf commented 2 years ago

Had the same thought...how does saving work here? Might be worth calling out as it's different then the usual VSCode behaviour.

smaddox-sf commented 2 years ago

@randi274 - Question on your settings - You're saying that you enabled the two settings below and then had the experience described above - do I have that right?

image

@gbockus-sf - When you Save, it saves the file to your Code Builder environment. Push or deploy would work the same, pulling code from your project on Code Builder and deploying/pushing to the org. Did you see other behavior?

gbockus-sf commented 2 years ago

@smaddox-sf The main difference I noticed when using code builder is it saves constantly, which is totally fine and better for a web based IDE. But this is different then the out of the box VSCode behaviour where it doesn't save until I execute a save for a particular file (or all files). The only reason this matters is it will change the behavior of users slightly from what they are use to doing if they already use vscode. It might also be different from how the dev console work if I'm remembering correctly (doesn't save until I trigger a save).

smaddox-sf commented 2 years ago

@sbudhirajadoc - This is a good difference in behavior to add to the doc page

smaddox-sf commented 2 years ago

doc updated (or to be updated)