CLI deletes resources on publish

[umulmrum]

Using 1.0.0-beta10 of the Puli CLI this happens:

puli publish --install will install new resources as expected (creates symlinks on localhost). If the same command is executed again, any new resources are again installed correctly, but resources that were published before are deleted from the SOURCE directory

In my case I built a Symfony bundle and added Resources/public/css/my.css, then published.
Then I added Resources/public/js/my.js and published again to create the js symlink. After that, my.css was deleted from the bundle. Then I published again and my.js was also gone.

I can't imagine a use case for this behaviour, so either I made some horrible mistake or this is a bug.
Let me know if I need to provide more information.

Thanks for your help!

[tgalopin]

Hello!

@webmozart this may be related to puli/repository#91, did we release a new CLI version when we fixed it in puli/repository beta10 ?

@umulmrum can you tell us what repository type you are using (you can do that by running puli config and check the key repository.type)? If you are using the filesystem one, you can try to use the JSON one (run puli config repository.type json), it could fix the issue.

[umulmrum]

@tgalopin thanks for the quick reply. Did only look in the open issues, but puli/repository#91 seems to be exactly the same problem.

repository.type already is json.

[tgalopin]

If your repository type is json, puli/repository#91 is not the problem but it may be related.

[thewilkybarkid]

I've encountered the same behaviour with beta10.

[thewilkybarkid]

Just spotted that the CLI beta10 was released before the repository beta10, so it can't contain the bug fix. I tried including the CLI as a local dependency and it does work as expected.

@webmozart Are you able to tag CLI beta11 soon?