feat: added async link generator to show/hide button

[alexpargon]

Button visibility depends on repository files.

Do not merge until the Pensive API

https://api.pennsieve.net/discover/datasets/${this.datasetId}/versions/1/assets/browse?path=&limit=5&offset=0&file=.hornet/manifest.json

Is in production, as it will not allow you to view/test the button

[cypress]

SPARC Vue3 Portal Testing    Run #783

Run Properties:   Passed #783  •  775e270abd: Merge branch 'main' into add-osparc-link-generator

Project	SPARC Vue3 Portal Testing
Branch Review	add-osparc-link-generator
Run status	Passed #783
Run duration	16m 32s
Commit	775e270abd: Merge branch 'main' into add-osparc-link-generator
Committer	Alejandro Parcet Gonzalez
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	39
Skipped	0
Passing	170
View all changes introduced in this branch ↗︎

[Copilot]

Pull Request Overview

This PR adds conditional visibility for the "Run on Osparc" button based on the presence of a .hornet/manifest.json file in the dataset repository. The button is now shown/hidden asynchronously by checking for the file's existence via the Pennsieve API.

Key changes:

• Replaced static osparcLink computed property with async getOsparcLink() method that checks for manifest file existence
• Modified button visibility to conditionally display based on API response
• Updated component styling to use consistent button widths

Reviewed Changes

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

File	Description
pages/datasets/[datasetId].vue	Added async link generation logic and replaced computed property with async method
components/DatasetDetails/SourceCodeInfo.vue	Updated button visibility logic and styling for consistent width handling

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.}

[alexpargon]

With this last change we introduce two global variables to:

• OSPARC_DISABLE_HORNET_BUTTON
  • Enables/Disables button visibility by not generating the URL and thus hiding the button
• OSPARC_ENABLE_CHECK_HORNET_MANIFEST
  • Enables/Disables the .hornet/cad_manifest.json file in case this endpoint does not work as expected

In case no globals are added to the environment variables, the button will be enabled and no cad_manifest.json will be searched for on pennsive.

This PR can be merged as soon as @pcrespov enables the new API endpoint on osparc side, or sooner with the Global variables setted to disable the button for now.

[pcrespov]

This PR can be merged as soon as @pcrespov enables the new API endpoint on osparc side

Everything ready on the osparc API

[egauzens]

@alexpargon Just a couple comments to address. Also, is there a dataset id that I can test this on?

[alexpargon]

@alexpargon Just a couple comments to address. Also, is there a dataset id that I can test this on?

Hello @egauzens !

I just solved the comments 😄.

About testing, right now as far as i know, no dataset has the proper .hornet/cad_manifest.json file, we should add a repository that has the proper structure to be sure.

[egauzens]

@alexpargon Just a couple comments to address. Also, is there a dataset id that I can test this on?

Hello @egauzens !

I just solved the comments 😄.

About testing, right now as far as i know, no dataset has the proper .hornet/cad_manifest.json file, we should add a repository that has the proper structure to be sure.

Hey @alexpargon I unresolved the conversations since I did not see the requested changes applied. Perhaps you forgot to push them?

[alexpargon]

@alexpargon Just a couple comments to address. Also, is there a dataset id that I can test this on?

Hello @egauzens !
I just solved the comments 😄.
About testing, right now as far as i know, no dataset has the proper .hornet/cad_manifest.json file, we should add a repository that has the proper structure to be sure.

Hey @alexpargon I unresolved the conversations since I did not see the requested changes applied. Perhaps you forgot to push them?

You were right! 🤯