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

UIREC-292: fix update item status on unreceive piece #484

Merged
merged 12 commits into from
Jan 30, 2024
Merged

Conversation

alisher-epam
Copy link
Contributor

@alisher-epam alisher-epam commented Jan 24, 2024

Purpose

UIREC-292 - fix update item status on unreceive piece according to the comment here Video source

Approach

Screen.Recording.2024-01-24.at.19.33.10.mov

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 Jan 24, 2024

Jest Unit Test Statistics

215 tests  +3   214 ✔️ +3   3m 30s ⏱️ -1s
  68 suites +1       1 💤 ±0 
    1 files   ±0       0 ±0 

Results for commit 32df8f3. ± Comparison against base commit a75beeb.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Jan 24, 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 32df8f3. ± Comparison against base commit a75beeb.

♻️ This comment has been updated with latest results.

@alisher-epam alisher-epam requested review from NikitaSedyx and a team January 25, 2024 13:15

return unreceive([currentPiece])
.then(() => {
onStatusChange(PIECE_STATUS.expected);
Copy link
Contributor

Choose a reason for hiding this comment

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

If I'm not mistaken, calling "unreceive" API updates the piece status and you don't need to do it again.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Let me check it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Screen.Recording.2024-01-29.at.13.31.27.mov

Copy link

Quality Gate Passed Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

1 New issue
0 Security Hotspots
94.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

@alisher-epam alisher-epam merged commit 0f78880 into develop Jan 30, 2024
6 checks passed
NikitaSedyx pushed a commit that referenced this pull request Feb 1, 2024
* UIREC-292: fix update item status on unreceive piece

* fix failing test

* test: improve test coverage

* refactor by adding custom `useUnreceive` hook

* tests: fix failing tests

* refactor useUnreceive hook

* update onUnreceivePiece callback function

* fix failing test case

* refactor onunrecieve callback

* tests: add test coverage

* update package.json interface versions

* revert package.json interface version due to wrong PR
NikitaSedyx pushed a commit that referenced this pull request Feb 21, 2024
* UIREC-292: fix update item status on unreceive piece

* fix failing test

* test: improve test coverage

* refactor by adding custom `useUnreceive` hook

* tests: fix failing tests

* refactor useUnreceive hook

* update onUnreceivePiece callback function

* fix failing test case

* refactor onunrecieve callback

* tests: add test coverage

* update package.json interface versions

* revert package.json interface version due to wrong PR
NikitaSedyx pushed a commit that referenced this pull request Feb 21, 2024
* UIREC-292: fix update item status on unreceive piece

* fix failing test

* test: improve test coverage

* refactor by adding custom `useUnreceive` hook

* tests: fix failing tests

* refactor useUnreceive hook

* update onUnreceivePiece callback function

* fix failing test case

* refactor onunrecieve callback

* tests: add test coverage

* update package.json interface versions

* revert package.json interface version due to wrong PR
@alisher-epam alisher-epam deleted the UIREC-292 branch March 11, 2024 07:21
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.

4 participants