-
Notifications
You must be signed in to change notification settings - Fork 3
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
UINV-469: Display all invoice versions in change log in fourth pane #825
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please respond to the comments. The rest are LGTM.
|
||
const { isLoading, data } = useQuery( | ||
[namespace, invoiceId], | ||
() => ky.get(`${AUDIT_INVOICE_API}/${invoiceId}`).json(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please provide a signal
from fn args to abort redundant requests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could please also include searchParams
to the query:
{
sortBy: 'event_date',
sortOrder: 'desc',
}
|
||
return { | ||
isLoading, | ||
versions: data?.invoiceAuditEvents || [], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please keep the default value as const outside the hook to prevent extra rendering (an array will create a new ref in the memory, which will trigger rerender of dependent components and hooks)
Quality Gate passedIssues Measures |
Purpose
UINV-469: Display all invoice versions in change log in fourth pane
Approach
Screen.Recording.2024-11-12.at.19.22.17.mp4
Screenshots
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.