✨ [Frontend] Feature: Saving pipeline

[odeimaiz]

What do these changes do?

This PR bring a small icon to the navigation bar that shows users when a study is being saved.

This makes sense only when users are dealing with pipelines, that's why it won't be enabled in standalone or app ui modes.

Reminder of how the save pipeline works:

• the frontend keeps a version of the last saved model in the backend
• if the model in the backend and the one in the frontend are not in sync, the frontend will try to patch the difference every 3" (non stop, if one fails it will retry)
• if the model in the backend and the one in the frontend are not in sync, this new icon is shown

Related issue/s

• somehow related to Webserver: Deleting a node should remove any reference to that node from the project workbench #8048

How to test

Dev-ops

[giancarloromeo]

Nice

[matusdrobuliak66]

Nice improvement 👍 thanks

[Copilot]

Pull Request Overview

This PR adds a visual "Saving..." indicator to the navigation bar by tracking a new savePending flag on the Study model. It introduces a periodic diff check in the StudyEditor to update that flag and binds it to a new icon in the NavigationBar.

• Adds a savePending property to Study and ignores it during serialization.
• Introduces DIFF_CHECK_INTERVAL and a saving timer in StudyEditor to set savePending.
• Binds study.changeSavePending events in NavigationBar to toggle a “Saving…” icon.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.

File	Description
services/static-webserver/client/source/class/osparc/navigation/NavigationBar.js	Bind savePending to a new "saving-study-icon" control and register the icon in left-items
services/static-webserver/client/source/class/osparc/desktop/StudyEditor.js	Define DIFF_CHECK_INTERVAL, start/stop a saving timer to call setSavePending, integrate into lifecycle
services/static-webserver/client/source/class/osparc/data/model/Study.js	Declare savePending property with change event and exclude it from serialization

Comments suppressed due to low confidence (2)

services/static-webserver/client/source/class/osparc/desktop/StudyEditor.js:108

• [nitpick] The name DIFF_CHECK_INTERVAL is generic—consider renaming it to something like SAVE_PENDING_CHECK_INTERVAL to clarify its specific role alongside AUTO_SAVE_INTERVAL.

    DIFF_CHECK_INTERVAL: 300,

services/static-webserver/client/source/class/osparc/desktop/StudyEditor.js:231

• There are no tests covering the new saving indicator or the logic in __startSavingTimer. Adding unit or integration tests would help ensure this behavior works correctly and prevent regressions.

        this.__startSavingTimer();

[GitHK]

very nice addition

[sanderegg]

very nice! Maybe check the copilot review

[odeimaiz]

@mergify queue

[mergify]

queue

🟠 Waiting for conditions to match

• -closed [📌 queue requirement]
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • label=🤖-automerge
    • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
    • #approved-reviews-by>=2
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by=0
    • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
    • #review-threads-unresolved=0
    • -conflict
    • -draft
    • base=master
    • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
    • label!=🤖-do-not-merge
    • any of: [🛡 GitHub branch protection]
      • check-skipped = deploy to dockerhub
      • check-neutral = deploy to dockerhub
      • check-success = deploy to dockerhub
    • any of: [🛡 GitHub branch protection]
      • check-success = system-tests
      • check-neutral = system-tests
      • check-skipped = system-tests
    • any of: [🛡 GitHub branch protection]
      • check-success = unit-tests
      • check-neutral = unit-tests
      • check-skipped = unit-tests
    • any of: [🛡 GitHub branch protection]
      • check-success = check OAS' are up to date
      • check-neutral = check OAS' are up to date
      • check-skipped = check OAS' are up to date
    • any of: [🛡 GitHub branch protection]
      • check-success = integration-tests
      • check-neutral = integration-tests
      • check-skipped = integration-tests
    • any of: [🛡 GitHub branch protection]
      • check-success = build-test-images (frontend) / build-test-images
      • check-neutral = build-test-images (frontend) / build-test-images
      • check-skipped = build-test-images (frontend) / build-test-images
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud