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 statusbar #5508
Add statusbar #5508
Conversation
initial CSS changes, implementing typsetyle
quick fix
middle Area + fileUpload refactor
Also support signaling from the status item to the status bar for context switches. Also set tsconfig for compilation in strict mode.
Impl context switches v4
added groups for icon and text
Refactor file path
Release 0.4.3
From the update-dependency script in @jupyterlab/buildutils: update-dependency --minimal --regex '^@jupyterlab/' ^next Then I edited the version of @types/react in package.json. Then I cleaned up the yarn.lock: git clean -dfx yarn install yarn check yarn-tools fix-duplicates yarn.lock > a mv a yarn.lock git clean -dfx yarn install
Update for jlab 0.35 prerelease.
This is a huge PR, and I agree we should merge ASAP and do cleanup/splitting in follow-ups. Thanks @saulshanabrook! |
Thanks @ian-r-rose for the cleanup |
Thanks! |
Just confirming that for |
I don't think this will be in a patch release, there is some more work to be done to further integrate this into the core. |
Thanks for the info! I'll keep an eye on the releases then. Also something to consider if I build from master - I've been considering spinning up a dev environment. |
We still cannot retrieve more than 250 commits for a PR, so exceptionally large PRs such as jupyterlab#5508 will still need some special-casing.
We still cannot retrieve more than 250 commits for a PR, so exceptionally large PRs such as jupyterlab#5508 will still need some special-casing.
Closes #5352 by adding statusbar to core
To create initial commit (from this guide on https://medium.com/@porteneuve/mastering-git-subtrees-943d29a798ec):
Then we added the name to some shared spots and edited some config files in it to make them more homogenous to the rest of the extensions.
We can merge this if the tests all pass and then work on splitting sone of the core logic into a
@jupyterlab/statusbar
package and moving out the registration of statusbar items to their respective extensions.