Skip to content
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: avoid re-render when using sidebar or appbar #366

Merged

Conversation

maartenbreddels
Copy link
Contributor

Before we had a 'fast path' which did not render the nav drawer and
appbar when not used. This caused a different component tree to be
rendered, which caused a re-render of the entire app.

This also causes our parent div to always be the same, which will
make the app behave more consistently (always 100vh parent).

Fixes #331

Copy link
Contributor Author

maartenbreddels commented Nov 3, 2023

Current dependencies on/for this PR:

This stack of pull requests is managed by Graphite.

@maartenbreddels maartenbreddels changed the base branch from 11-01-feat_support_for_ipyvue_and_ipyvuetify_v3 to master November 3, 2023 11:07
@maartenbreddels maartenbreddels force-pushed the 11-03-fix_avoid_re-render_when_using_sidebar_or_appbar branch 2 times, most recently from f202a5e to dcbec29 Compare November 3, 2023 11:12
Before we had a 'fast path' which did not render the nav drawer and
appbar when not used. This caused a different component tree to be
rendered, which caused a re-render of the entire app.

This also causes our parent div to always be the same, which will
make the app behave more consistently (always 100vh parent).

Fixes #331
otherwise screenshots will be different every time
@maartenbreddels maartenbreddels force-pushed the 11-03-fix_avoid_re-render_when_using_sidebar_or_appbar branch from dcbec29 to 0489c81 Compare November 3, 2023 14:53
@maartenbreddels maartenbreddels merged commit 3884d6a into master Nov 3, 2023
21 checks passed
maartenbreddels added a commit that referenced this pull request Nov 16, 2023
Note that this fixes #366 which was a breaking change, which was
not yet released.  So this is not a breaking change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Components appear to be loaded in duplicate
1 participant