Skip to content
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

issue number 2074 resolved #4350

Merged
merged 4 commits into from
Jan 11, 2024
Merged

Conversation

cerdo03
Copy link
Contributor

@cerdo03 cerdo03 commented Dec 7, 2023

Summary

Description of the change(s) you made

Fixes #2074
As stated, the native_name has been changed to first_native_name as native_name can be a comma separated list of names.

Manual verification steps performed

  1. Login and click on edit channel details
  2. The dropdown of language is there which can be verified
  3. The dropdown currently shows the list of languages which can be changed

References

Comments


Contributor's Checklist

PR process:

  • If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
  • If this includes an internal dependency change, a link to the diff is provided
  • The docs label has been added if this introduces a change that needs to be updated in the user docs?
  • If any Python requirements have changed, the updated requirements.txt files also included in this PR
  • Opportunities for using Google Analytics here are noted
  • Migrations are safe for a large db

Studio-specifc:

  • All user-facing strings are translated properly
  • The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
  • All UI components are LTR and RTL compliant
  • Views are organized into pages, components, and layouts directories as described in the docs
  • Users' storage used is recalculated properly on any changes to main tree files
  • If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

  • Code is clean and well-commented
  • Contributor has fully tested the PR manually
  • If there are any front-end changes, before/after screenshots are included
  • Critical user journeys are covered by Gherkin stories
  • Any new interactions have been added to the QA Sheet
  • Critical and brittle code paths are covered by unit tests

Reviewer's Checklist

This section is for reviewers to fill out.

  • Automated test coverage is satisfactory
  • PR is fully functional
  • PR has been tested for accessibility regressions
  • External dependency files were updated if necessary (yarn and pip)
  • Documentation is updated
  • Contributor is in AUTHORS.md

@MisRob MisRob requested review from akolson and AllanOXDi and removed request for LianaHarris360 December 7, 2023 14:36
ozer550
ozer550 previously requested changes Dec 8, 2023
@@ -106,7 +106,7 @@
},
methods: {
languageText(item) {
return this.$tr('languageItemText', { language: item.native_name, code: item.id });
return this.$tr('languageItemText', { language: item.first_native_name, code: item.id });
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @cerdo0! It seems like the value of item.first_native_name is undefined. The output now only shows the code of the language in the dropdown.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

may be something like this could work?
const firstNativeName = item.native_name.split(',')[0].trim()
cc @MisRob?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#2074 is a pretty old issue, so yes, it seems first_native_name is obsolete. I don't see it anywhere in the codebase https://github.com/search?q=repo%3Alearningequality%2Fstudio+first_native_name&type=code.

@ozer550 your suggestion makes sense. I'd just suggest confirming that

native_name can be a comma separated list of names

is still a valid remark.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes I think it is! If we see for the code (nv) then it shows comma separated name.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @MisRob @ozer550 ,
I have made the changes as suggested by you guys. Please review my changes.

Copy link
Member

@akolson akolson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look correct to me. Please run the lint formatter to fix the linting issues reported on your pr(yarn run lint-frontend:format). Thanks @cerdo03. Adding @radinamatic for some more manual QA.

Also, noting that it looks like the value native_name may not require splitting afterall as similar code snippets in the code base suggest otherwise. @bjester?

@cerdo03
Copy link
Contributor Author

cerdo03 commented Dec 17, 2023

@akolson I have run the lint formatter and fixed the lint issues. Please review.

@bjester bjester requested a review from ozer550 December 19, 2023 16:31
@MisRob
Copy link
Member

MisRob commented Jan 10, 2024

Thank you, @cerdo03, apologies for delayed response, we were on holidays. We will re-review.

Copy link
Member

@akolson akolson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes checkout and manual QA done shows the dropdown works as expected. Thank you very much for your contribution @cerdo03!

You are welcome to help with more issues in any of our 3 repositories, if you'd like. Also, please review the community guidelines in the links below before contributing.

@bjester bjester merged commit 7cd3468 into learningequality:unstable Jan 11, 2024
9 checks passed
@akolson akolson mentioned this pull request Aug 13, 2024
@akolson akolson mentioned this pull request Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use first_native_name in LanguageDropDown.vue instead of native_name
5 participants