-
Notifications
You must be signed in to change notification settings - Fork 308
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
[WIP] Implement jupyter server listextensions #151
[WIP] Implement jupyter server listextensions #151
Conversation
So, where we previously did |
Hi @vidartf , This implements The last one is still supported for backwards compatibility reasons. This PR is just a first shot further to a discussion I had with @Zsailer. We said we would further see how we should progress with that. I have added a |
Granted, the same could be said about i.e.
If there are more actions that you want to support (install/remove/enable/disable?) then the above seems more composable than |
If it is a technical problem to pass three command words instead of two, either of these would be more readable:
|
I agree with the comments above. I've opened a #157 as an alternative approach, implementing a |
Closing this in favor of #157 |
* wip * update deps and add comment * wip add react components * add styling * more updates * clean up * finish component
This PR implement the extensions listing as a subapp of jupyter server.