Skip to content

Conversation

@Dmytro-Melnyshyn
Copy link
Contributor

@Dmytro-Melnyshyn Dmytro-Melnyshyn commented Jan 14, 2026

Description

Previously, the service point modal window appeared for the app, because checkout was added in https://github.com/folio-org/ui-servicepoints/blob/master/src/eventHandlers.js#L33. After changes were made in webpack and ui-sevicepoints, all the modules that need this modal should add "subscribesTo": ["servicepoints"] to package.json to replace the hard-coded list.

Refs

https://folio-org.atlassian.net/browse/UICHKOUT-882

Screenshots

image

Approach

Refs

Screenshots

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

Jest Unit Test Results

419 tests  ±0   419 ✅ ±0   20s ⏱️ -1s
 22 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 206d01c. ± Comparison against base commit a131fea.

@sonarqubecloud
Copy link

@Dmitriy-Litvinenko Dmitriy-Litvinenko requested a review from a team January 14, 2026 12:20
@Dmytro-Melnyshyn Dmytro-Melnyshyn merged commit dc9ef09 into master Jan 14, 2026
15 checks passed
@Dmytro-Melnyshyn Dmytro-Melnyshyn deleted the UICHKOUT-882 branch January 14, 2026 15:07
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