Force fetch creates results at inconsistent location

[jeffhube]

If I run force fetch -t ApexClass, it creates two directories in the working directory: src, which is empty, and metadata, which contains package.xml and the classes directory. If I then run the same command again, the package.xml and classes directory are now created in the src folder instead.

v0.22.64 on Windows 10

[jeffhube]

Looking at https://github.com/heroku/force/blob/7a0d36e775d1ac3c68d77dd644be1002209243d0/config.go#L60 , these two directories are supposed to be symlinked, which won't work on Windows by default unless running as admin.

It would be nice if the output were consistently written to either src or metadata, to avoid this weird behavior when symlinking fails.

[dcarroll]

Thanks Jeff for the info. It actually is kind of weird on the Mac as well. I am looking at trying to piggy back on the project structure that Salesforce DX is using which is quite different. Sorry for the wierdness, I'll do my best to try to resolve this as soon as I can.

…

On Thu, Mar 2, 2017 at 1:36 PM, Jeff Hube ***@***.***> wrote: Looking at https://github.com/heroku/force/blob/ 7a0d36e/config.go#L60 , these two directories are supposed to be symlinked, which won't work on Windows by default unless running as admin. It would be nice if the output were consistently written to either src or metadata, to avoid this weird behavior when symlinking fails. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#378 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHGHsjYR4FXH-5Z4U8Il6ExVRUFXHcGks5rhzZTgaJpZM4MRi3b> .

-- Thanks, Dave