-
Notifications
You must be signed in to change notification settings - Fork 2
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
UIBULKED-315 Group holdings record properties using optgroup component #396
Conversation
Kudos, SonarCloud Quality Gate passed! |
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.
Functionally, this looks great, but i18n is incomplete and some names related to holdings (I think it should always be holdings
, right?) are inconsistent.
}); | ||
|
||
return { | ||
holdingNotes, |
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.
For consistency in naming, I think this should be holdingsNotes
rather than holdingNotes
. What do you think?
label: formatMessage({ id: 'ui-bulk-edit.layer.options.holdings.temporaryLocation' }), | ||
disabled: false }, | ||
disabled: false, | ||
categoryName: 'Holdings location' |
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.
categoryName
must be i18n'ed.
{ | ||
value: OPTIONS.PERMANENT_HOLDINGS_LOCATION, | ||
label: formatMessage({ id: 'ui-bulk-edit.layer.options.holdings.permanentLocation' }), | ||
disabled: false, | ||
categoryName: 'Holdings location' |
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.
categoryName
must be i18n'ed.
@zburke thanks for your commets, it was merged by mistake. All your comments makes sense and will be addressed! Don't have an idea why it's possible merge without approval.. |
I'll follow up with DevOps on that one. I'm curious about it too! |
Purpose
https://issues.folio.org/browse/UIBULKED-315
After this PR we will have holdings notes in select + grouping:
Approach
TODOS and Open Questions
Learning
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.