UIQM-715: Reuse existing ids for fields after saving a record to avoid re-rendering and be able to focus on a field by ref.

[Dmytro-Melnyshyn]

Purpose

Move focus to the last focused field after saving a record.

Approach

Ids of fields are generated again after the record is saved, this creates new elements for each field and prevents the use of ref to focus the element. The approach is to reuse existing ids.

TODOS and Open Questions

Issues

UIQM-715

Screencasts

2024-10-22_17h25_50.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   47 suites  ±0   2m 51s ⏱️ +4s
475 tests +2  475 ✅ +2  0 💤 ±0  0 ❌ ±0 
478 runs  +2  478 ✅ +2  0 💤 ±0  0 ❌ ±0 

Results for commit aeada80. ± Comparison against base commit 60749b5.

♻️ This comment has been updated with latest results.

[mariia-aloshyna]

fix lint issues please

[BogdanDenis]

Looks good, just need to fix ESlint issues

[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 SonarCloud