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

Marital status dropdown settings.separated translation - updated #2124

Conversation

mahak-juriani
Copy link
Contributor

@mahak-juriani mahak-juriani commented Jul 26, 2024

What kind of change does this PR introduce?
Bugfix

Issue Number:

Fixes #2115 by @mahak-juriani

Did you add tests for your changes?

Yes

Snapshots/Videos:

Talawa.-.Settings.-.Separated.translation.resolved.mp4

Summary

Under Settings page, when Marital status of the user is edited - the label for Separated is shown as settings.separated instead of SEPARATED.
The issue is resolved in this Pull Request

Resolves #2115

Does this PR introduce a breaking change?
No

Have you read the contributing guide?

Yes

Summary by CodeRabbit

  • Bug Fixes

    • Corrected spelling of "separated" in English, French, Hindi, Spanish, and Chinese translation files for improved localization accuracy.
  • Tests

    • Introduced a new test case for verifying the marital status dropdown in the User Portal's Settings component, enhancing test coverage and functionality verification.

Copy link
Contributor

coderabbitai bot commented Jul 26, 2024

Walkthrough

The recent changes focus on correcting spelling errors in various translation files across multiple languages, specifically the term "separated." Additionally, a new constant related to marital status options has been introduced in the test suite for the User Portal's Settings component, enhancing the testing of dropdown functionality. These adjustments aim to improve accuracy in translations and ensure robust testing coverage.

Changes

File Change Summary
public/locales/en/translation.json, public/locales/fr/translation.json, public/locales/hi/translation.json, public/locales/sp/translation.json, public/locales/zh/translation.json Corrected the spelling of "separated" from "seperated" in translation files.
src/screens/UserPortal/Settings/Settings.test.tsx Introduced mockMaritalStatusEnum for testing marital status dropdown options and added a test case for verification.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Dropdown
    participant Translations

    User->>Dropdown: Clicks marital status dropdown
    Dropdown->>Translations: Fetch options
    Translations-->>Dropdown: Return ["Single", "Married", "Separated", "Divorced", ...]
    Dropdown-->>User: Display options
Loading

Assessment against linked issues

Objective Addressed Explanation
Marital status dropdown shows correct translation for "Separated" (#2115)
Fix spelling errors in language files (#2115)

Poem

In fields of green, I hop and play,
With changes bright, we cheer today!
Spelling fixed, all translations right,
Marital status shines so bright.
🐇✨ Hooray for fixes, let joy abound,
In every dropdown, may love be found!

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Copy link

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

  1. The overall code coverage drops below the target threshold of the repository
  2. Any file in the pull request has code coverage levels below the repository threshold
  3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Congratulations on making your first PR! 🎊 If you haven't already, check out our Contributing Guidelines and PR Reporting Guidelines to ensure that you are following our guidelines for contributing and creating PR.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7f71db5 and f9c1d93.

Files selected for processing (6)
  • public/locales/en/translation.json (1 hunks)
  • public/locales/fr/translation.json (1 hunks)
  • public/locales/hi/translation.json (1 hunks)
  • public/locales/sp/translation.json (1 hunks)
  • public/locales/zh/translation.json (1 hunks)
  • src/screens/UserPortal/Settings/Settings.test.tsx (2 hunks)
Files skipped from review due to trivial changes (5)
  • public/locales/en/translation.json
  • public/locales/fr/translation.json
  • public/locales/hi/translation.json
  • public/locales/sp/translation.json
  • public/locales/zh/translation.json
Additional comments not posted (2)
src/screens/UserPortal/Settings/Settings.test.tsx (2)

110-135: LGTM! The new constant mockMaritalStatusEnum is well-defined.

This improves readability and maintainability by centralizing the marital status options.


398-508: LGTM! The new test case Marital Status dropdown value verification is comprehensive.

This test case ensures that the dropdown functionality works as expected and enhances the clarity of the test by using mockMaritalStatusEnum.

Copy link

codecov bot commented Jul 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.48%. Comparing base (7f71db5) to head (f9c1d93).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2124      +/-   ##
===========================================
+ Coverage    97.46%   97.48%   +0.01%     
===========================================
  Files          233      233              
  Lines         6551     6551              
  Branches      1919     1919              
===========================================
+ Hits          6385     6386       +1     
+ Misses         151      150       -1     
  Partials        15       15              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@palisadoes palisadoes merged commit 5448735 into PalisadoesFoundation:develop Jul 27, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants