✨ [Frontend] Check if I can write_functions

[odeimaiz]

What do these changes do?

In order to show the Create Functions section, the user needs to belong to a group that is allowed to write_functions.

Related issue/s

• related to Disable create function ability osparc-issues#1901
• follows Add global functions user permissions 🎨 #7868
• follows ✨ Add Controller for /me/function-permissions Endpoint in Functions Domain #7901

How to test

Dev-ops

[Copilot]

Pull Request Overview

This PR ensures that the “Create Functions” section is only shown when the user’s group has the write_functions permission by:

• Adding a new functionPermissions endpoint and loading both general and function-specific permissions at startup
• Refactoring Permissions to store and expose group-level and function-level permissions via checkMyGroupCanDo and checkFunctionPermissions
• Updating UI components (NodeOptions, ResourceDetails) to use the new permission checks and automatically rebuild layouts

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
services/static-webserver/client/source/class/osparc/widget/NodeOptions.js	Renamed buildLayout to private __buildLayout and applied it on node property; switched permission check to checkMyGroupCanDo
services/static-webserver/client/source/class/osparc/desktop/WorkbenchView.js	Removed manual buildLayout call now handled by the property apply
services/static-webserver/client/source/class/osparc/desktop/MainPage.js	Preload both general and function permissions before rendering
services/static-webserver/client/source/class/osparc/data/Resources.js	Added functionPermissions resource definition
services/static-webserver/client/source/class/osparc/data/Permissions.js	Introduced __permissions and __functionPermissions, methods to fetch and check them
services/static-webserver/client/source/class/osparc/dashboard/ResourceDetails.js	Changed plugin-disabled check to use checkFunctionPermissions

Comments suppressed due to low confidence (3)

services/static-webserver/client/source/class/osparc/data/Permissions.js:300

• [nitpick] Consider adding a JSDoc comment to explain the purpose of fetchFunctionPermissions and its relationship with __functionPermissions.

fetchFunctionPermissions: function() {

services/static-webserver/client/source/class/osparc/desktop/MainPage.js:73

• New startup permission-fetching logic should be covered by tests to ensure both general and function permissions are loaded before the UI displays.

preloadPromises.push(osparc.data.Permissions.getInstance().fetchPermissions());

services/static-webserver/client/source/class/osparc/data/Permissions.js:317

• The variable functionPermissions is undefined here; it should reference this.__functionPermissions[action].

return functionPermissions[action];

[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

[odeimaiz]

@mergify 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

[pcrespov]

thx