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

UIPFU-100 Add modal title prop support #280

Merged
merged 3 commits into from
Oct 25, 2024
Merged

UIPFU-100 Add modal title prop support #280

merged 3 commits into from
Oct 25, 2024

Conversation

NikitaSedyx
Copy link
Contributor

@NikitaSedyx NikitaSedyx commented Oct 24, 2024

Purpose

https://folio-org.atlassian.net/browse/UIPFU-100

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.

@NikitaSedyx NikitaSedyx requested review from a team and Terala-Priyanka October 24, 2024 10:09

This comment has been minimized.

Copy link

github-actions bot commented Oct 24, 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 51588d2. ± Comparison against base commit 78f1547.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Oct 24, 2024

Jest Unit Test Statistics

16 tests  ±0   16 ✔️ ±0   25s ⏱️ -1s
  3 suites ±0     0 💤 ±0 
  1 files   ±0     0 ±0 

Results for commit 51588d2. ± Comparison against base commit 78f1547.

♻️ This comment has been updated with latest results.

Copy link

@NikitaSedyx NikitaSedyx merged commit 980402e into master Oct 25, 2024
6 checks passed
@NikitaSedyx NikitaSedyx deleted the UIPFU-100 branch October 25, 2024 09:02
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