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

UITEN-298 - supply correct translation ids #410

Merged
merged 1 commit into from
Jul 4, 2024
Merged

Conversation

Terala-Priyanka
Copy link
Contributor

@Terala-Priyanka Terala-Priyanka commented Jul 3, 2024

Purpose

UITEN-298 - Incorrect translation id is being provided in reading room settings

Approach

TODOS and Open Questions

Learning

Pre-Merge Checklist

Before merging this PR, please go through the following list and take appropriate actions.

  • I've added appropriate record to the CHANGELOG.md
  • Does this PR meet or exceed the expected quality standards?
    • Code coverage on new code is 80% or greater
    • Duplications on new code is 3% or less
    • There are no major code smells or security issues
  • Does this introduce breaking changes?
    • If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
    • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

  • What other modules will these changes impact?
  • Do JIRAs exist to update the impacted modules?
    • If not, please create them
    • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
    • Do they have all they appropriate links to blocked/related issues?
  • Are the JIRAs under active development?
    • If not, contact the project's PO and make sure they're aware of the urgency.
  • Do PRs exist for these changes?
    • If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.

While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

Copy link

github-actions bot commented Jul 3, 2024

Jest Unit Test Statistics

    1 files  ±0  28 suites  ±0   2m 15s ⏱️ -12s
106 tests ±0  94 ✔️ ±0  12 💤 ±0  0 ±0 
108 runs  ±0  96 ✔️ ±0  12 💤 ±0  0 ±0 

Results for commit 1a6bf44. ± Comparison against base commit b8c2509.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Jul 3, 2024

BigTest Unit Test Statistics

0 tests  ±0   0 ✔️ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ±0 

Results for commit 1a6bf44. ± Comparison against base commit b8c2509.

♻️ This comment has been updated with latest results.

Copy link

sonarcloud bot commented Jul 3, 2024

@Terala-Priyanka Terala-Priyanka merged commit c70e491 into master Jul 4, 2024
6 checks passed
@Terala-Priyanka Terala-Priyanka deleted the UITEN-298 branch July 4, 2024 11:27
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.

3 participants