🎨 [Frontend] Hide template used to register function

[odeimaiz]

What do these changes do?

As discussed, this PR hides the template that is used to register a function and adds some project_metadata to it.

Related issue/s

• closes Template created through "Create Function" does show up at templates in osparc-issues#1896

How to test

Dev-ops

[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

[wvangeit]

Thanks @odeimaiz

[Copilot]

Pull Request Overview

This PR hides the function-registration template by default and adds custom metadata to it, while also updating the resources API to support these changes.

• Adds a hidden: true flag when publishing templates and hidden: false when copying studies
• Introduces __updateTemplateMetadata to patch project metadata before registering the function
• Extends osparc.data.Resources with a hidden URL parameter and an updateMetadata PATCH endpoint

Reviewed Changes

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

File	Description
services/static-webserver/client/source/class/osparc/study/CreateFunction.js	Mark template as hidden, split creation into metadata update and function registration
services/static-webserver/client/source/class/osparc/desktop/MainPage.js	Pass hidden: false when copying a study to a new template
services/static-webserver/client/source/class/osparc/data/Resources.js	Add hidden query param to postToTemplate and define updateMetadata endpoint

Comments suppressed due to low confidence (3)

services/static-webserver/client/source/class/osparc/study/CreateFunction.js:315

• [nitpick] The custom metadata key hidden overlaps with the template creation flag. Consider renaming this field to clarify its purpose (e.g., template_description or metadata_note).

"hidden": "Base template for function"

services/static-webserver/client/source/class/osparc/study/CreateFunction.js:290

• The new hidden flag on template creation and the updateMetadata workflow lack corresponding unit or integration tests. Consider adding tests to verify both behaviors.

"hidden": true,

services/static-webserver/client/source/class/osparc/study/CreateFunction.js:312

• [nitpick] This method would benefit from a brief JSDoc comment explaining its responsibility, parameters, and any important side effects.

__updateTemplateMetadata: function(templateData) {

[odeimaiz]

@Mergifyio queue

[mergify]

queue

🟠 Waiting for conditions to match

• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #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
    • label=🤖-automerge
    • 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