Fix: issuable search filter locale issue
What does this MR do and why?
Reason
For some reasons, the current search filter token is using the key Assignee and Reviewer but these two entries were used
by other components with plural form.
For Chinese or other languages like Japanese, plural and singular form are the same, when we use __() method to translate
the key here it will be using the first value in the screenshot.
Normally we use n__('Assignee', '%d Assignees', count) to translate the key.
In this MR, I added namespace for two keys Assignee and Reviewerto avoid ambiguity
/cc @prajnamas @orozot @qk44077907
Screenshots or screen recordings
Wrong case
After fix
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- Boot GDK
- Go to any project you have
- Go to Merge Request
- After the page loaded, click the search input in the middle of the page.
- Observe.
For English users, this will make no differences, but for other languages, we can benefit from it after the entries get translated.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.