Skip to content

feat(dashboards): Allow removing of wrapper in lazyrender #68998

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

Merged
merged 7 commits into from
Apr 16, 2024

Conversation

scttcper
Copy link
Member

@scttcper scttcper commented Apr 16, 2024

This reverts commit be24d67

Updating react-lazyload added an additional div wrapper to use as the visible ref. Dashboard styles rely on lots of overflow and full height styles and a wrapping div breaks them since you want the overflow scrollbars to be on that element.

This adds the ability for our lazy render to remove the wrapper once the component is on the screen.

good test dashboard

Once the dashboard widget is on the screen, remove the lazy placeholder and just render the children.
@scttcper scttcper requested review from JonasBa and a team April 16, 2024 16:46
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Apr 16, 2024
Copy link

codecov bot commented Apr 16, 2024

Bundle Report

Changes will decrease total bundle size by 15.42kB ⬇️

Bundle name Size Change
app-webpack-bundle-array-push 26.29MB 26.29MB ⬆️
sentry-webpack-bundle-array-push (removed) 26.31MB ⬇️

@scttcper scttcper enabled auto-merge (squash) April 16, 2024 17:58
@scttcper scttcper merged commit 06f9689 into master Apr 16, 2024
@scttcper scttcper deleted the scttcper/dashboards-lazyload branch April 16, 2024 18:04
@github-actions github-actions bot locked and limited conversation to collaborators May 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants