Some users would like to try the v2 canvas. We would also like some users to try this.
There are two parts to this:
- loading the /a/ route from ApiServer
- calling the api
Switching /a/ over
To allow users to switch over, we could provide a new route that routes to F#
To fully switch the /a/CANVASNAME route to the Apiserver, while still allowing /api/CANVASNAME to go to OCaml, we would need:
Users don't care too much about this, it's just loading a page. So maybe the second part is more important.
Switching /api/ over
If we add a ?fsharp-backend option to the client, it could use a different api, perhaps /api-private-for-testing-only/
This allows the user to opt-in for API calls.
Some users would like to try the v2 canvas. We would also like some users to try this.
There are two parts to this:
Switching /a/ over
To allow users to switch over, we could provide a new route that routes to F#
/a-testing-fsharp/CANVASNAMETo fully switch the
/a/CANVASNAMEroute to the Apiserver, while still allowing/api/CANVASNAMEto go to OCaml, we would need:Users don't care too much about this, it's just loading a page. So maybe the second part is more important.
Switching /api/ over
If we add a ?fsharp-backend option to the client, it could use a different api, perhaps /api-private-for-testing-only/
This allows the user to opt-in for API calls.