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
Fix UI problems when some of the package versions mismatch #7182
Fix UI problems when some of the package versions mismatch #7182
Conversation
Thanks for making a pull request to JupyterLab! To try out this branch on binder, follow this link: |
This looks reasonable to me, and running it in dev mode works too. @telamonian - do you think it's ready to merge? |
@jasongrout Yes. I have thoroughly tested it, both in dev mode and against a broken |
Thanks! |
@meeseeksdev backport to 1.1.x |
… versions mismatch
…2-on-1.1.x Backport PR #7182 on branch 1.1.x (Fix UI problems when some of the package versions mismatch)
Fixes #7158 as well |
References
fixes #7181
and a whole bunch of other recent issues
Code changes
The latest version of eg
ui-components
relies on recent changes made across the codebase. There's currently an issue where a1.0.x
installation of Jlab (up to1.0.7
) will pull in the newest version of a package under certain conditions (eg install an extension and then rebuild). This in turn was causing various problems with the appearance of Jlab. This PR fixes three such appearance bugs, listed in order of descending severity:ui-components
relies on changes made to the.svg
loader configuration inwebpack.config.js
. This PR adds a shim that allows the new icon stuff inui-components
to work properly with.svg
files loaded the old way.apputils
relies on changes made to the schema inthemes.json
in the latest version ofapputils-extension
. The PR adds an explicit check for those changes, and graceful handling if they aren't there.User-facing changes
No more appearance glitches for
v1.0.0-1.0.7
Backwards-incompatible changes