We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some users would like to try the v2 canvas. We would also like some users to try this.
There are two parts to this:
To allow users to switch over, we could provide a new route that routes to F#
/a-testing-fsharp/CANVASNAME
To fully switch the /a/CANVASNAME route to the Apiserver, while still allowing /api/CANVASNAME to go to OCaml, we would need:
/a/CANVASNAME
/api/CANVASNAME
Users don't care too much about this, it's just loading a page. So maybe the second part is more important.
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.
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
Finished this in #3619.
pbiggar
No branches or pull requests
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/CANVASNAME
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.
The text was updated successfully, but these errors were encountered: