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
A few parts from the default BinderHub frontend could be reused for the gallery:
BinderImage
EventSource
There is an issue on the binderhub repo about the long term planning for the frontend: jupyterhub/binderhub#774
One way forward could be to have a common client package that would provide a basic set of functionalities to interact with a BinderHub deployment.
The text was updated successfully, but these errors were encountered:
There is now https://github.com/jupyterhub/binderhub/tree/main/js/packages/binderhub-client, published as @jupyterhub/binderhub-client on NPM. I've been cleaning it up a lot more in the last week or so, and the next version out should be pretty usable
@jupyterhub/binderhub-client
Sorry, something went wrong.
Nice thanks @yuvipanda for the heads-up!
Marking as "help wanted" in case someone would like to take a closer look at how this package could be used in this repo.
No branches or pull requests
A few parts from the default BinderHub frontend could be reused for the gallery:
BinderImage
abstraction, that would hide implementation details such as the use of anEventSource
There is an issue on the binderhub repo about the long term planning for the frontend: jupyterhub/binderhub#774
One way forward could be to have a common client package that would provide a basic set of functionalities to interact with a BinderHub deployment.
The text was updated successfully, but these errors were encountered: