-
Notifications
You must be signed in to change notification settings - Fork 2
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
Scaffolding UI #4
Conversation
@@ -0,0 +1,14 @@ | |||
{ | |||
"title": "@jupyter-suggestions/jupyter-suggestions-core", |
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.
Is the @jupyter-suggestions
scope a placeholder, or should we go with something like this for the final package name?
If so I guess it would be fine to already create the org on npm
. Otherwise we could also use the @jupyter
or @jupyterlab
scopes later.
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.
you are right, I'm going to switch to @jupyter
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.
Do we need to ask for permission to publish packages under this org?
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 so far!
Happy to merge so it's easier to iterate. Thanks for working on this!
User-facing changes