Closed acuarica closed 5 months ago
If we do not remove the Session API endpoints from the spec, we might want to give a stronger warning than “not supported”. In fact no client code running in a browser is ever going to be able to call these endpoints (unless the corresponding domain is configured as an allowedOrigin
in the server session).
Other than that, looks good to me.
@Nana-EC @svienot I've updated the message, pls take a look.
Description:
Remove session endpoints so that we can share the api-docs. Also fix the server drop-down which was showing always the local dev server.
I have included both prod and local server in the drop-down, but maybe the Current REST API server suffices.
Default server value
When the user opens the servers drop-down
Session endpoints label
Related issue(s):
Fixes #
Notes for reviewer:
Checklist