Sync command doesn't do what documentation says about locize-cli

[megaturbo]

For posterity: It was a bug introduced by a previous release, which was quickly fixed.

Thanks, closing.

[adrai]

I just tried to reproduce both use cases, but they behave exactly as they should.
Can you please provide more information?
If you add the --dry true argument, you see what the CLI would do without actually doing it.
You can also write us an email to [email protected] with the exact command line arguments you are using etc...

[megaturbo]

Thanks for the very fast answer. I can answer here for now.

I previously set my project id and api key through:

export LOCIZE_PROJECTID=<project_id>​
export LOCIZE_API_KEY=<api_key>​

The command I run is:

yarn dlx locize-cli sync --path public/locales

Dry run example

I remove the about key in my public/locales/en/translation.json file. If I run

> yarn dlx locize-cli sync --path public/locales --dry true

checking remote (locize)...
checking local (<project_dir>/public/locales) only reference language...
calculate diffs...
adding 206 keys in en/translation...
would add key1, key2, key3,... in en/translation...
syncing...
FINISHED

So, now I indeed have 206 keys, and it does not show about in the list of keys to update. However it does not remove it on my web app (without the --dry true)

Should it output something about removal when using --dry true ?

Edit:

Also, the fact it says "adding 206 keys" while they already exist on locize. Does it mean there's something wrong already ? (I setup locize with locize migrate if that helps)

[adrai]

I assume the version settings in your locize project (I assume 'latest') is not set to auto-publish mode, but to manual publish mode....
If you tell me the project-id (please via email), I can check that.
btw: https://github.com/locize/locize-cli?tab=readme-ov-file#synchronize-locize-with-your-repository-or-any-other-local-directory