UIU-3503: Add condition to check for non-empty servicePoints before showing handler in withServicePoints component. Do not show loading when saving a user record to prevent triggering the 'Are you sure' modal.

[Dmytro-Melnyshyn]

Purpose

1. When the current user edits their record, and there are no service points, the "Select service point" modal shouldn't appear during the user record saving (this can be reproduced if the user logs in as the user they want to edit, with no service points assigned, edits any field and hits save).
2. Prevent showing the "Are you sure?" modal when saving a record. Some resources are re-fetched during form save, which remounts custom fields components, triggering form.change(), which makes the form dirty and prevents redirection by showing the "Are you sure?" modal (this can be reproduced only when there is a Single select/Multiselect/Radio button custom field, which makes the form dirty in edit mode, and when a user changes the user role, and then hits save).

Approach

1. Add a check for non-empty servicePoints.
2. Display loading only when opening the page. Do not show it during form save.

TODOS and Open Questions

Issues

https://folio-org.atlassian.net/browse/UIU-3503

Screencasts

The bug

2025-12-26_17h57_59.mp4

After the fix

2025-12-29_12h16_25.mp4

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]

Jest Unit Test Results

    1 files  ±0    274 suites  ±0   5m 49s ⏱️ ±0s
1 312 tests ±0  1 309 ✅ ±0  3 💤 ±0  0 ❌ ±0 
1 353 runs  ±0  1 350 ✅ ±0  3 💤 ±0  0 ❌ ±0 

Results for commit c12dc02. ± Comparison against base commit 4f42410.

This pull request removes 2 and adds 2 tests. Note that renamed tests count towards both.

UserEdit should cancel form ‑ UserEdit should cancel form
UserEdit should submit form and call update ‑ UserEdit should submit form and call update

UserEdit should render loading ‑ UserEdit should render loading
withDeclareLost when servicePoints array is empty should not show HandlerManager ‑ withDeclareLost when servicePoints array is empty should not show HandlerManager

♻️ This comment has been updated with latest results.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud