Ambiguous --compare-modification-time flag behavior about locize-cli

[adrai]

Just tried to reproduce your second case:

this seems to work for me.

---

The last case without --compare-modification-time behaves as intended, because "your local repository is the master":

---

In general the CLI will always compare with what is published. To see what is actually published, check your namespace: https://docs.locize.com/integration/api#fetch-namespace-resources

---

The logic of --compare-modification-time is simple: it just compares the last-modified header of the published translations with the mtime of the local file. The newer datetime is the master namespace.

---

So when should --compare-modification-time be used and when not?

-> Usually, the developers will only work locally, and only with the reference language. So, adding new keys or removing old keys would automatically be synchronized with locize, but existing value updates in locize would be synched back locally.
Often this is the default process. => in this case --compare-modification-time is not necessary.

But it may be there is a mix in the process, so sometimes new keys gets added to locize directly sometimes only locally, etc... In this situation --compare-modification-time true is favorable.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ravecat]

@adrai thank you for answer, could you take advice how to find modification time for locize translation. every sync values from locize rewrite of local translation values, it looks like remote changes always take precedence

[adrai]

Sorry, I don't understand your question. Can you please elaborate?

[ravecat]

@adrai you mentioned

it just compares the last-modified header of the published translations with the mtime of the local file. The newer datetime is the master namespace.

I have abilty to get mtime

So, have any ability to get modiified time for locize translation version? Because every sync remote translation rewrite local changes and I want to compare mtime and modification time from header

[adrai]

Like said, the last-modified header of your published translations (https://docs.locize.com/integration/api#fetch-namespace-resources)

i.e. for the https://locize.com website the downloaded translations are: https://api.locize.app/3d0aa5aa-4660-4154-b6d9-907dbef10bb2/production/en/landingpage
In the response header you'll find it:

[ravecat]

Thanks, will compare these