UIREC-412 Update 'Send claim' action to use pieces.send-claims
interface
#624
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://folio-org.atlassian.net/browse/UIREC-412
This pull request updates the 'Send claim' action in the
ui-receiving
module to utilize thepieces.send-claims
interface, aligning with the latest backend changes.Approach
The approach taken in this pull request focuses on maintaining compatibility with updated backend interfaces, improving code quality, and ensuring seamless integration with the
pieces.send-claims
interface. Here's a breakdown of the approach:1. Alignment with Backend Updates
pieces.send-claims
).pieces.send-claims
specifications.2. Code Refactoring
Screenshots
chrome_Omk1fvISLw.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.