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

UIQM-735: Return also sub permissions in useUserTenantPermissions hook. #761

Merged
merged 6 commits into from
Nov 26, 2024

Conversation

Dmytro-Melnyshyn
Copy link
Contributor

@Dmytro-Melnyshyn Dmytro-Melnyshyn commented Nov 25, 2024

Purpose

Be able to edit MARC bibliographic record in the member tenant having required permissions in the sub-permissions.

Approach

Add also sub-permissions to the set of permissions returned by useUserTenantPermissions.

Issues

UIQM-735

Screencast

2024-11-25_14h55_48.mp4

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.

Copy link

github-actions bot commented Nov 25, 2024

Jest Unit Test Statistics

    1 files  ±0    43 suites  ±0   2m 39s ⏱️ -1s
517 tests +1  517 ✔️ +1  0 💤 ±0  0 ±0 
519 runs  +1  519 ✔️ +1  0 💤 ±0  0 ±0 

Results for commit 156b123. ± Comparison against base commit a4c1649.

♻️ This comment has been updated with latest results.

@Dmytro-Melnyshyn Dmytro-Melnyshyn force-pushed the UIQM-735 branch 2 times, most recently from 2ed66c4 to 755defc Compare November 25, 2024 16:48
@Dmytro-Melnyshyn Dmytro-Melnyshyn requested review from BogdanDenis and a team November 26, 2024 07:23
@Dmytro-Melnyshyn Dmytro-Melnyshyn merged commit 9eb5666 into b8.0 Nov 26, 2024
5 checks passed
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