You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be good if we subtracted entries in "missing key" state from the total of translated keys. That way, the total count should better match what is actually translated and the overall percentage should be correct again.
The text was updated successfully, but these errors were encountered:
This is actually more tricky than one would think.
Reviews cannot be used for this, because they are computed asynchronously after a property file has been persisted.
The completion state however is computed directly as part of the serialization process and for performance reasons it simply compares the amount of serialized Key/Value pairs with the amount of keys in the template. The Template is not loaded or evaluated for this, the value comes directly from the Database.
Currently I only see two possibilites:
The Missing Key review actively modifies the completion state of resource
During serialization the template must be loaded as well and each translation key must be compared against the template. That comes with a performance penalty.
None of these sound like a perfect solution. Do you have an idea for an alterantive?
It would be good if we subtracted entries in "missing key" state from the total of translated keys. That way, the total count should better match what is actually translated and the overall percentage should be correct again.
The text was updated successfully, but these errors were encountered: