-
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
UISACQCOMP-166: add unassignDonor
to default formatters
#728
Conversation
Jest Unit Test Statistics 1 files ±0 146 suites +1 4m 24s ⏱️ +30s Results for commit 2f71a3e. ± Comparison against base commit be0e6f9. This pull request removes 1 and adds 3 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
lib/Donors/DonorsList.js
Outdated
}) => { | ||
const stripes = useStripes(); | ||
const canViewOrganizations = stripes.hasPerm('ui-organizations.view'); | ||
const formatter = useMemo(() => { | ||
return formatterProp || getDonorsListFormatter({ canViewOrganizations }); | ||
}, [canViewOrganizations, formatterProp]); | ||
|
||
const anchoredRowFormatter = (rowProp) => acqRowFormatter(rowProp); |
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.
Why create a function that doesn't do anything when you can pass in the original?
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.
good point
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.
updated
Kudos, SonarCloud Quality Gate passed! |
Purpose
UISACQCOMP-166 - Updated default visible columns for the container. The purpose we don't need to pass the
unassignDonor
for form-based donors list. And move remove button on the right side of the row.Approach
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.