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

Add reusable custom hook useVersionHistoryValueResolvers #839

Merged
merged 5 commits into from
Dec 6, 2024

Conversation

azizjonnurov
Copy link
Contributor

@azizjonnurov azizjonnurov commented Dec 4, 2024

https://folio-org.atlassian.net/browse/UISACQCOMP-235

Purpose

It will be reused in ui-modules just as ui-invoice

Approach

Create custom reusable hook useVersionHistoryValueResolvers

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 Dec 4, 2024

Jest Unit Test Statistics

    1 files  ±0  225 suites  +1   3m 55s ⏱️ -4s
602 tests +6  600 ✔️ +6  2 💤 ±0  0 ±0 
605 runs  +6  603 ✔️ +6  2 💤 ±0  0 ±0 

Results for commit 1ddbaa1. ± Comparison against base commit 03b5d13.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Dec 4, 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 1ddbaa1. ± Comparison against base commit 03b5d13.

♻️ This comment has been updated with latest results.

@azizjonnurov azizjonnurov requested a review from a team December 4, 2024 13:49
Copy link
Contributor

@usavkov-epam usavkov-epam left a comment

Choose a reason for hiding this comment

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

Please update the changelog

lib/hooks/index.js Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Contributor

@usavkov-epam usavkov-epam left a comment

Choose a reason for hiding this comment

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

Looks good to me!
Please resolve one small comment regarding the changelog.

Copy link

sonarcloud bot commented Dec 5, 2024

@azizjonnurov azizjonnurov requested review from NikitaSedyx, alisher-epam and a team December 5, 2024 07:12
@azizjonnurov azizjonnurov merged commit a6b569e into master Dec 6, 2024
6 checks passed
@azizjonnurov azizjonnurov deleted the UISACQCOMP-235 branch December 6, 2024 07:09
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