-
Notifications
You must be signed in to change notification settings - Fork 18
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
🚀 Add awesomebar
-like UX to launch button
#528
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 2cf97f3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 14 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
That is so slick! |
const { | ||
className, | ||
defaultMessage, | ||
copiedMessage, | ||
invalidLinkFallback, | ||
buildLink, | ||
copiedMessageDuration, | ||
} = props; |
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.
Nothing functional (besides variable aliases) is changed here, just cleanups
This PR closes #507 by changing the launch button UI to detect the target.
It is motivated by 2i2c-org/infrastructure#5348 in 2i2c's sprint planning.
This feature is intended to bring us closer to a time in which the distinction between JupyterHub and BinderHub becomes increasingly less relevant.
There are some nuances encoded in this UX; we assume that the JupyterHub uses
nbgitpuller
. In future, we (2i2c) would like to unify the features of nbgitpuller and mybinder so that the language for addressing contents can be drawn closer together.2025-02-04.16-36-14.mp4
To Do
In future, this feature should probably use a reducer — the business logic already feels more complicated than I would like.