Testresults: Add ability to split enso translations and own translations about localisation HOT 13 CLOSED

Also needed: Update of documentation

from localisation.

New core files are empty - I think this is OK?

By empty you mean they have all the keys and the values are null?

from localisation.

Question: Should the state of Key collector get stored locally? At the moment its Off after every reload?
Nope. We want to use this flag with care.

from localisation.

We should enso lang files to php artisan vendor:publish --force --tag='enso-assets'

Correct.

Needed Change: Add php artisan localisation:merge to composer post-update-cmd

Correct.

Do you want to make this changes or I will?

Thanks.

from localisation.

from localisation.

from localisation.

Strange. When I create a new language i get jsons with the keys and null values.

I will make the changes tomorrow, and test again.

from localisation.

from localisation.

the first extra()

from localisation.

Added both.

Right now, on every automatic hit on addKey a merge (all) command executes. This is not optimal. On a page with 20 new labels, and having 20 languages, the app will make 20 requests and 20*20 merges.

I think that the best solution is to cancel the logic that does the auto merge, and do the merge manually, once all the labels were gathered.

from localisation.

I think that the best solution is to cancel the logic that does the auto merge, and do the merge manually, once all the labels were gathered.

We can add a "merge" button to FE below "key collector switch"?

from localisation.

I think that it would fit better somewhere in the localisation structure.. maybe on the EditTexts page.

from localisation.

also ok

from localisation.