UIREC-305 View piece status change log #473
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mariia-aloshyna
requested changes
Dec 26, 2023
| it('should render piece status log list', () => { | ||
| renderComponent(); | ||
|
|
||
| expect(screen.getByText('ui-receiving.piece.statusChangeLog.column.status')); |
There was a problem hiding this comment.
Suggested change
| expect(screen.getByText('ui-receiving.piece.statusChangeLog.column.status')); | |
| expect(screen.getByText('ui-receiving.piece.statusChangeLog.column.status')).toBeInTheDocument(); |
There was a problem hiding this comment.
Good catch, @mariia-aloshyna, thanks! Updated
mariia-aloshyna
approved these changes
Dec 27, 2023
Terala-Priyanka
approved these changes
Jan 1, 2024
usavkov-epam
force-pushed
the
UIREC-305
branch
from
a9fdf1e to
ccf0dbb
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
https://issues.folio.org/browse/UIREC-305
As users are making decisions about whether or not to claim pieces. The system must capture that activity and display it on the piece record.
Approach
Screenshot
chrome_L33NPn05M2.mp4
Pre-Merge Checklist
Before merging this PR, please go through the following list and take appropriate actions.
If there are breaking changes, please STOP and consider the following:
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.