Sync returns a different result for "auto-publish" mode and without it about locize-cli HOT 8 CLOSED

fyi: v7.12.0 (which includes the --unpublished true command line argument) has just been released

from locize-cli.

This warning should probably explain that: https://github.com/locize/locize-cli#synchronize-locize-with-your-repository-or-any-other-local-directory

This is an expected behaviour.

from locize-cli.

@adrai yes, that looks like answer, but I have two questions

1. I've saw tips in locize doc, which recommended disable "auto-pulish" for production (unfinished translations, sensitive information). So, synchronization is not incompatible with manual publish?
2. what is standart mode?
3. Are you plan to unify the synchronization behavior? some teams can't switch to auto-publish

thank you for a great tool

from locize-cli.

1. yes, normally you only have to synchronize translations in versions in which you are currently working, and those usually are using auto-publish.
2. standard mode = auto publish
3. don't know exactly what you mean with this question, sorry. Can you elaborate?

from locize-cli.

@adrai Oh, sorry

Third question - Are you plan to unify the synchronization behavior? some teams can't switch to auto-publish. CLI command force rewrite pending version (version which waiting publich trigger)

from locize-cli.

There is a feature in progress, that will ignore the published translations and will use the translations in the database.
There will be a cli argument, something like --unpublished true that will enable this.
But this will lead to the generation of private downloads, because it will use this endpoint: https://docs.locize.com/integration/api#fetch-filter-the-unpublished-namespace-resources

from locize-cli.

@adrai thank you for answers, I've cleared all the points

from locize-cli.

@adrai thank you a lot, I will try new flag

from locize-cli.