Deploy on Save

Is your feature request related to a problem? Please describe. I’m running the new change_set_based_tools and a compile on save is desperately needed.

Describe the solution you’d like Setting you can add to cause it to run deploy this source file to org command on save

Describe alternatives you’ve considered Could probably use a “Run on save extension” but it would be much nicer to have it supported out of the box

Internal Work Item: W-5552627

[NikitaChizhik]

Please , could you do deploy on save. (I should press ctrl+save then with mouse choose file from left sidebar and right click and choose to deploy source to org. and repeat it every time I want to deploy) - that’s a nightmare.)

Note: I am dealing with not scratch org. I develop against any org(simple). Thats my case for now. VSCode version is latest and salesforcePack version is latest.

Now I made a shortcut(ctrl+d) to deploy current open file . BUT it also doesnt work. it writes to me Cannot read property ‘fsPath’ of undefined.

Please look at these two bugs (which prevent me and many others not to use vsCode and this SF plugin).

Thanks for your project and work.

[smrobert09]

@renatoliveira @omniphx @ntotten We have an extension that adds the file system tracking. It creates a hash table of the folder structure, detects changes, and allows a ‘deploy all changes’ type command.

SFDX creates the hash file automatically on ‘force:source:retrieve --manifest’ (the sourcePathInfos.json file under .sfdx/orgs/<orgUsername>/sourcePathInfos.json). The problem is that it deletes as soon as the command finishes, making us rebuild it or try to capture/copy it. I know sandboxes aren’t source tracking orgs, meaning that we override changes on every push, but if that file were left in place, this would be an easy win. Is this something we can request from the CLI team @ntotten ?

We could easily then create a pull request for this into the official package.