Skip to content
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

Merged
merged 3 commits into from
Oct 16, 2023

Conversation

vashjs
Copy link
Contributor

@vashjs vashjs commented Oct 16, 2023

Purpose

https://issues.folio.org/browse/UIBULKED-315

After this PR we will have holdings notes in select + grouping:

image

Approach

TODOS and Open Questions

Learning

Pre-Merge Checklist

Before merging this PR, please go through the following list and take appropriate actions.

  • I've added appropriate record to the CHANGELOG.md
  • Does this PR meet or exceed the expected quality standards?
    • Code coverage on new code is 80% or greater
    • Duplications on new code is 3% or less
    • There are no major code smells or security issues
  • Does this introduce breaking changes?
    • If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
    • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

  • What other modules will these changes impact?
  • Do JIRAs exist to update the impacted modules?
    • If not, please create them
    • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
    • Do they have all they appropriate links to blocked/related issues?
  • Are the JIRAs under active development?
    • If not, contact the project's PO and make sure they're aware of the urgency.
  • Do PRs exist for these changes?
    • If so, have they been approved?

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.

@github-actions
Copy link

github-actions bot commented Oct 16, 2023

Jest Unit Test Statistics

    1 files  ±0    25 suites  ±0   2m 25s ⏱️ +45s
160 tests ±0  159 ✔️ ±0  1 💤 ±0  0 ±0 
163 runs  ±0  162 ✔️ ±0  1 💤 ±0  0 ±0 

Results for commit 9713a6f. ± Comparison against base commit fa6a61f.

♻️ This comment has been updated with latest results.

@github-actions
Copy link

github-actions bot commented Oct 16, 2023

BigTest Unit Test Statistics

0 tests  ±0   0 ✔️ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ±0 

Results for commit 9713a6f. ± Comparison against base commit fa6a61f.

♻️ This comment has been updated with latest results.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

86.0% 86.0% Coverage
0.0% 0.0% Duplication

@vashjs vashjs requested a review from a team October 16, 2023 08:44
Copy link
Member

@zburke zburke left a 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.

package.json Show resolved Hide resolved
});

return {
holdingNotes,
Copy link
Member

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'
Copy link
Member

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'
Copy link
Member

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.

@vashjs vashjs merged commit 988d3fb into master Oct 16, 2023
5 checks passed
vashjs added a commit that referenced this pull request Oct 16, 2023
@vashjs
Copy link
Contributor Author

vashjs commented Oct 16, 2023

@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..

@zburke
Copy link
Member

zburke commented Oct 16, 2023

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants