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

UISAUTHCOM-23 Display toast message for saving and editing authorization roles #37

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

usavkov-epam
Copy link
Contributor

@usavkov-epam usavkov-epam commented Sep 26, 2024

Purpose

https://folio-org.atlassian.net/browse/UISAUTHCOM-23

Approach

Handle success and error requests and display corresponding toast messages.

Additionally, accept the tenantId prop in the policy form to specify the tenant, which is used to send requests.

Screenshot

chrome_Sgipgj4FSI.mp4

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.

@usavkov-epam usavkov-epam self-assigned this Sep 26, 2024
Copy link

github-actions bot commented Sep 26, 2024

Jest Unit Test Statistics

    1 files  ±0    49 suites  ±0   1m 52s ⏱️ -1s
145 tests +5  145 ✔️ +5  0 💤 ±0  0 ±0 
152 runs  +5  152 ✔️ +5  0 💤 ±0  0 ±0 

Results for commit ce84ed2. ± Comparison against base commit 343b78f.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Sep 26, 2024

BigTest Unit Test Statistics

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

Results for commit ce84ed2. ± Comparison against base commit 343b78f.

♻️ This comment has been updated with latest results.

@usavkov-epam usavkov-epam requested review from a team and aidynoJ September 26, 2024 17:42
@artem-blazhko artem-blazhko requested a review from a team September 27, 2024 07:52
Copy link

sonarcloud bot commented Sep 30, 2024

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