-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
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
fix: remove session endpoints and fix server drop-down #118
Conversation
Signed-off-by: Luis Mastrangelo <[email protected]>
Signed-off-by: Luis Mastrangelo <[email protected]>
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 Other than that, looks good to me. |
Signed-off-by: Luis Mastrangelo <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, suggestion on text since the open source code should reference 1 single deployed instance name like hashscan
Co-authored-by: Nana Essilfie-Conduah <[email protected]> Signed-off-by: Luis Mastrangelo <[email protected]>
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