-
Notifications
You must be signed in to change notification settings - Fork 32
🐛 [Frontend] Fix: service catalog #7856
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
A fix to prevent incomplete or null service metadata from breaking the service catalog by filtering out services missing inputs or outputs.
- Adds guard in service list retrieval to exclude null services and those without
inputsoroutputs - Updates catalog refresh to operate on the cleaned list
Comments suppressed due to low confidence (2)
services/static-webserver/client/source/class/osparc/workbench/ServiceCatalog.js:205
- Add unit tests covering the scenario where a service has missing inputs or outputs to verify the new filtering logic.
this.__servicesLatest = servicesList.filter(service => service !== null && service.inputs && service.outputs);
services/static-webserver/client/source/class/osparc/workbench/ServiceCatalog.js:204
- [nitpick] Consider expanding this comment to specify exactly which metadata fields are required (e.g.,
inputsandoutputs) and why they are critical for the catalog.
// first check metadata is complete
|
|
@Mergifyio queue |
🟠 Waiting for conditions to match
|
|
Will checke validations in the backend as well |



What do these changes do?
If a service's metadata, which information is not complete or is null (e.g.
/project/servicesand this doesn't exist) makes into the service cache, it might break the service catalog. This PR takes care of this corner case (found in S4L staging).Buggy:

Related issue/s
How to test
Dev-ops