Reflect theme changes without a refresh

[garsonbyte]

By leveraging IThemeManager.themeChanged, we can listen on theme change signals and rebuild the theme object in response. This allows CSS variable changes to reflect in the MUI theme without having to refresh the page.

(@dlqqq) I've verified that this PR:

• Fixes Chat UI input loses border when theme is switched #138
• Fixes fix MUI text theme #200

[welcome]

Thanks for submitting your first pull request! You are awesome! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please make sure you followed the pull request template, as this will help us review your contribution more quickly.

You can meet the other Jovyans by joining our Discourse forum. There is also a intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[JasonWeill]

@garsonbyte Thank you so much for opening this! It looks like the linting test is failing. Can you try running jlpm run prettier locally, then committing and pushing any changes?

[dlqqq]

@garsonbyte Thank you so much for working on this! This issue had totally escaped my attention. Your PR worked great out-of-the-box. 🎉

There were a few additional changes that I wanted to make to your branch before merging. I've submitted these as a pull request on your fork: garsonbyte#1

If you're OK with these suggestions, then please merge that PR, which will include those commits in this PR. Then I'll approve and merge this PR. 👍

[dlqqq]

@garsonbyte Sorry for the delay in merging your PR. I rebased the branch onto the latest version of main, and these changes will be included in the next release. Thank you very much for working on this! 🎉

BTW, you should add your Git email to your GitHub profile so your avatar shows up in the commit history. Right now, only my avatar is showing, even though you authored the first commit. The email you used to sign your commit is [email protected]. GitHub won't show your avatar in the commit history until you add that email to your GitHub account. 👋

[welcome]

Congrats on your first merged pull request in this project! 🎉

Thank you for contributing, we are very proud of you! ❤️

[dlqqq]

@meeseeksdev please backport to 1.x

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 1.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 ca03e2c9a846344c379d50ccbe8323f7e0c7b1ed

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #575: Reflect theme changes without a refresh'

4. Push to a named branch:

git push YOURFORK 1.x:auto-backport-of-pr-575-on-1.x

5. Create a PR against branch 1.x, I would have named this PR:

"Backport PR #575 on branch 1.x (Reflect theme changes without a refresh)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.