-
Notifications
You must be signed in to change notification settings - Fork 25
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
Update select labels #1768
Update select labels #1768
Conversation
❌ Deploy Preview for dev-storybook-bloom failed. 🔨 Explore the source changes: 2522dc8 🔍 Inspect the deploy log: https://app.netlify.com/sites/dev-storybook-bloom/deploys/6144fcfc9baee00007452cfd |
✔️ Deploy Preview for dev-bloom ready! 🔨 Explore the source changes: 2522dc8 🔍 Inspect the deploy log: https://app.netlify.com/sites/dev-bloom/deploys/6144fcfcb3d62a0008c9e25a 😎 Browse the preview: https://deploy-preview-1768--dev-bloom.netlify.app |
✔️ Deploy Preview for dev-partners-bloom ready! 🔨 Explore the source changes: 2522dc8 🔍 Inspect the deploy log: https://app.netlify.com/sites/dev-partners-bloom/deploys/6144fcfc4dc35a0008a8b714 😎 Browse the preview: https://deploy-preview-1768--dev-partners-bloom.netlify.app |
✔️ Deploy Preview for clever-edison-cd22c1 ready! 🔨 Explore the source changes: c09d4f5 🔍 Inspect the deploy log: https://app.netlify.com/sites/clever-edison-cd22c1/deploys/6128c97ccfc45300074631be 😎 Browse the preview: https://deploy-preview-1768--clever-edison-cd22c1.netlify.app |
✔️ Deploy Preview for clever-edison-cd22c1 ready! 🔨 Explore the source changes: 63dea39 🔍 Inspect the deploy log: https://app.netlify.com/sites/clever-edison-cd22c1/deploys/6128ca3d5d284a00071cec5b 😎 Browse the preview: https://deploy-preview-1768--clever-edison-cd22c1.netlify.app |
@@ -1032,7 +1032,14 @@ | |||
"individualUnits": "Individual Units", | |||
"delete": "Delete this Unit", | |||
"deleteConf": "Do you really want to delete this unit?", | |||
"eligibility": "Eligibility" | |||
"eligibility": "Eligibility", | |||
"typeOptions": { |
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.
These translations already exist, we don't want to have any duplicates
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.
These translations still exist elsewhere under preferredUnit
I think we can delete these added translations and use the others yeah?
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.
@dominikx96 , can you please make this update.
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.
I think the options for preferredUnit are a little different and we may not want a one to one here, since those have a + option.
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.
See comment about translations :)
@pbn4 is there any option and sense to update keys:
|
@emilyjablonski , can you take a look at this again. |
I commented two days ago on the duplicate translations still |
* Update select labels * Update changelog * Remove duplicated translation * Fix json structure * updates translations and fixes unrelated issue with unit form * reverts some changes on tranlsation keys Co-authored-by: Dominik Barcikowski <dominik@airnauts.com> Co-authored-by: Sean Albert <smabert@gmail.com>
Pull Request Template
Issue
Addresses #1761
Description
Updates select options to use translations.
Type of change
How Can This Be Tested/Reviewed?
Open the "Add unit" form and check the "Unit Type" field options. They should be translated.
Checklist: