Allow preferring specific TranslationModelRecord versions for local testing
Categories
(Firefox :: Translations, enhancement)
Tracking
()
People
(Reporter: nordzilla, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 obsolete files)
Description
When we release new versions of Translations models in Remote Settings, our algorithm automatically defaults to taking the maximum compatible version.
This makes it hard to test an older version in a side-by-side comparison once a newer model version is released, since the algorithm always chooses the highest record version.
We should implement an easy way for developers to specify a preferred model record version in order to do a side-by-side comparison once the version is released.
Steps to implement
Rework the getMaxVersionRecords()
algorithm to check a pref for a preferred record version.
Tests to implement
Ensure all test cases pass for the existing algorithm.
Add new test cases that consider the preferred version.
Reporter | ||
Comment 1•1 year ago
|
||
Refactors the isBetterRecordVersion() function to take the
entire record, instead of just the version. This refactor
does not change any logic, but makes changes more
straightforward in the following patch.
Reporter | ||
Comment 2•1 year ago
|
||
Reworks the isBetterRecordVersion() function to check
a user preference for a preferred record version,
which developers can set explicitly in order to test
an older record version if desired.
Depends on D206400
Updated•1 year ago
|
Updated•1 year ago
|
Updated•11 months ago
|
Updated•11 months ago
|
Reporter | ||
Updated•9 months ago
|
Description
•