feat(frontend): implement scalar integration

[rozzilla]

Fixes #73

QA done ✅

[mcollina]

I have a rough feeling this is not going to work for nested/not-exposed services. For those, you'd need to route the messages through watt-admin and then through the Control.

[rozzilla]

I have a rough feeling this is not going to work for nested/not-exposed services. For those, you'd need to route the messages through watt-admin and then through the Control.

I don't see how we can do that using scalar so 🤔

I think we need a slightly better messaging in case there is no OpenAPI for the service, or possibly just a relatively simple UI to send fetch() calls.

Considering the point above, and the fact that scalar adds a lot of dependencies (>13k lines updated in the package-lock.json 😱) and "noise" in the CSS (some classes of the frontend repo were overridden), I suggest we go for the second option, to always have a simple UI to send fetch calls.

This will always work, it will be way slimmer and easy to implement, and users will always see the same interface (rather than scalar for some services, and custom UI for others). @mcollina WDYT?

[mcollina]

We did this before in Meraki: https://github.com/platformatic/meraki. Take a look.

[rozzilla]

We did this before in Meraki: https://github.com/platformatic/meraki. Take a look.

@mcollina updated with a similar approach (using an internal /proxy endpoint)

[mcollina]

Is it possible to remove the /api/proxy/32620/services/service as shown here?

---

Looking at this, is this possible to add some text like "Open it at http://.."

[rozzilla]

Is it possible to remove the `/api/proxy/32620/services/service` as shown here?

I see it in the image you shared. I don't get what I should update...

Looking at this, is this possible to add some text like "Open it at http://.."

It's not clear to me what URL I should show here 🤔

[rozzilla]

@mcollina updated ✅

[mcollina]

lgtm