-
Notifications
You must be signed in to change notification settings - Fork 859
Use "variant name [variant tag]" format everywhere (review, write, profile) #4865
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use "variant name [variant tag]" format everywhere (review, write, profile) #4865
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @HarikalarKutusu, looks good for me from the backend perspective. There are FE tests that are failing though and have to be fixed and one merge conflict (due to the recent random sentences update).
Missed one test :( @moz-rotimib, any comment/request is very much welcome. |
.../contribution/sentence-collector/write/sentence-input-and-rules/sentence-input-and-rules.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR fixes/implements:
[BUG]
variant_token
is used instead ofvariant_name
in the Review screen #4840 (this time for real).[BUG] Bad source for variant name translations (should get from database) #4721
Also removes translation warnings in the console.
TO-CHECK: Effect of variant related settings in the profile => Added a commit to handle that case (see note below)
TO-DO: Better layout and test with different length sentences => seems OK
@moz-dfeller & @moz-rotimib :
Select
component interface is a bit limiting, but can be fixed in refactoring.Large screen with long textual parts test (seems OK):

Same on smaller screens (seems OK):

Profile:

Write:
