Allows the user to sync the packages folder in the clone project with the original project by clicking a button in the ClonesManagerWindow, which is very useful when developing embedded packages.
I've noticed there have been multiple requests and PRs for this feature, and it would be very useful to me since I frequently work on embedded packages for my projects, so here's my take on implementing it. Just a simple button on the original project's ClonesManagerWindow that copies/replaces the Packages folder in the clone project with the Packages folder from the original project.
No more weird/misleading behavior when you forget that your clones and original have separate package versions (esp. when developing embedded packages). It's a good sanity check when debugging.
The developer has full control over when the sync happens.
There is less "mental overhead" than a symlink, it's a straight copy.
Allows the user to sync the packages folder in the clone project with the original project by clicking a button in the ClonesManagerWindow, which is very useful when developing embedded packages.
I've noticed there have been multiple requests and PRs for this feature, and it would be very useful to me since I frequently work on embedded packages for my projects, so here's my take on implementing it. Just a simple button on the original project's ClonesManagerWindow that copies/replaces the Packages folder in the clone project with the Packages folder from the original project.
I don't believe this is an acceptable work around. Closing and reopening the project takes time and hinders rapid iteration during development: https://github.com/VeriorPies/ParrelSync/wiki/Troubleshooting-&-FAQs#why-isnt-my-newly-installed-package-being-synced-to-clone-editors
Benefits are