You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The temp folder is used mainly for safety reasons.
if we download directly into Project directory then it will overwrite all changed files unconditionally and, if used with text editor plugin like vim-force.com, the plugin will have no chances to track changes, backup files or warn user about the changes they are about to lose.
Also, SFDC returns default package name 'unpackaged' as opposed to 'src', so direct copy would not be possible anyway. I can not remember in details but think with salesforce Ant plugin you get different top folder names depending on the config. I could theoretically do the same in tooling-force.com, but this may cause problems for managed packages which I do not want to debug.
For unattended cases - taking into account that --tempFolderPath is user defined - it shall be trivial to add a line or two to copy files to the relevant destination in the script which calls tooling-force.com.
Currently it downloads to a temp folder under unpackaged.
This works, but why not just refresh to the folder the package.xml is in?
The text was updated successfully, but these errors were encountered: