feat: add deeplink to service

[SpecialAro]

Pre-flight Checklist

Please ensure you've completed all of the following.

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.

Description of Change

Enables activating a service by using ferdium://service/:serviceId

Motivation and Context

This PR fixes #1243. In the future, It would be interesting to also handle ferdium://service/:serviceName and present the user with different options if there is more than one recipe with the same name

Checklist

• My pull request is properly named
• The changes respect the code style of the project (pnpm prepare-code)
• pnpm test passes
• I tested/previewed my changes locally

Release Notes

notes: Added feature for activating a service from deep link using the service id.

[vraravam]

Very nice if this works @SpecialAro !

[SpecialAro]

Very nice if this works @SpecialAro !

I've tested on my macOS (had to build the app to test, as ferdium-dev protocol was opening an Electron window that was not ferdium) but it worked!

The downside is having to call the serviceId and not the name of a service 🥲 but in the future maybe we can improve this with a better logic

[ylluminate]

This looks really interesting. Can you give us some use-cases and examples for a more clear picture and various scenarios?

[KrystianLesniak]

I am testing this feature on 6.5.0-nightly6 and unfortunately at first glance it does not seem to work on Windows 11 x64.

For example, results from ferdium://service/gmail or ferdium://service/:gmail show a blank purple screen when the application is already running:

If the application is not currently running, deeplink will just start the application without running the specified service. It will show the first service just like normal startup.

This is my first experience with this feature, when I have some more time I will create full issue at repository describing problem.

[Alphrag]

For example, results from ferdium://service/gmail or ferdium://service/:gmail show a blank purple screen when the application is already running:

@KrystianLesniak Thanks for trying it. As mentioned by @SpecialAro above:

The downside is having to call the serviceId and not the name of a service 🥲 but in the future maybe we can improve this with a better logic

this means that you would need to call the url with the full serviceId, which is something that looks like d8d5eeb9-36be-4ec7-9ac7-d4abdfdabf01 (this for example is mine for Discord). Thus, I would need to call ferdium://service/d8d5eeb9-36be-4ec7-9ac7-d4abdfdabf01 instead of ferdium://service/discord.
I don't know what is the best way to find the values of the serviceId, but a good one is to go into the menu and click on Help -> Import/Export Configuration Data in order to export the .ferdium-data file. This is a json file which for each of your service contains the name, serviceId and other settings associated to it.

[KrystianLesniak]

Got it! I've referenced to "id" from these documents:
https://github.com/ferdium/ferdium-recipes/blob/main/docs/integration.md
https://github.com/ferdium/ferdium-recipes/blob/main/docs/configuration.md

That's why I misunderstood what "id" property is. I will try it later, thanks!

[SpecialAro]

Hey!

Thank you @Alphrag for clarifying! That is indeed what I meant.

Nevertheless, I'll try to implement the ferdium://service/:recipeId (e.g. ferdium://service/gmail) in the future. But, as I said, we have to probably handle a logic if a user has more than 1 service with the same recipe id...

[SpecialAro]

Got it! I've referenced to "id" from these documents:

Indeed does documents refer to a Recipe Id (which would be used in the approach that I just written). I'll try to make a simple approach that activates the first service and then we can think of improving it.

[KrystianLesniak]

I've quickly tested with correct service Id exported from .ferdium-data file and unfortunately the same issues as mentioned above happens.

So it's just launching application without changing to correct service or blank purple screen when application is already launched.

[SpecialAro]

I've quickly tested with correct service Id exported from .ferdium-data file and unfortunately the same issues as mentioned above happens.

So it's just launching application without changing to correct service or blank purple screen when application is already launched.

I just noticed a bug. You are using Windows, am I right? I bet @Alphrag used macOS (as I did when coding - but now just tested with windows)

basically windows is adding a string with "--allow-file-access-from-files" for some reason... causing it to crash:

[KrystianLesniak]

I've quickly tested with correct service Id exported from .ferdium-data file and unfortunately the same issues as mentioned above happens.
So it's just launching application without changing to correct service or blank purple screen when application is already launched.

I just noticed a bug. You are using Windows, am I right? I bet @Alphrag used macOS (as I did when coding - but now just tested with windows)

basically windows is adding a string with "--allow-file-access-from-files" for some reason... causing it to crash:

Yes, bug occurs at Windows 11 x64. Great and quick bug source finding @SpecialAro !

[Alphrag]

I just noticed a bug. You are using Windows, am I right? I bet @Alphrag used macOS (as I did when coding - but now just tested with windows)

Yeah I've tested it on mac, and doing something like open ferdium://service/d8d5eeb9-36be-4ec7-9ac7-d4abdfdabf01 works perfectly. Now I've also tried with my AppImage on windows using xdg-open but this launches Ferdium as usual and discards the link

[KrystianLesniak]

I've quickly tested with correct service Id exported from .ferdium-data file and unfortunately the same issues as mentioned above happens.
So it's just launching application without changing to correct service or blank purple screen when application is already launched.

I just noticed a bug. You are using Windows, am I right? I bet @Alphrag used macOS (as I did when coding - but now just tested with windows)

basically windows is adding a string with "--allow-file-access-from-files" for some reason... causing it to crash:

Hello everyone.
Sorry to bother you in closed PR, but it is hard for me to dig through countless changelogs. Do you know if it is fixed yet?