feat: apply visible lazy-loading guard to canvas chart components#9005
Merged
feat: apply visible lazy-loading guard to canvas chart components#9005
visible lazy-loading guard to canvas chart components#9005Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Canvas components use an
IntersectionObserverto set avisiblestore totruethe first time a component scrolls into the viewport. This pattern was already applied to KPI and leaderboard components to prevent data queries from firing off-screen, but chart components were not covered.Threads
visible: Readable<boolean>fromCanvasChart.svelte→getChartDataForCanvas→BaseChart.createChartDataQuery→ each chart providerhttps://linear.app/rilldata/issue/APP-157/optimize-data-fetching-based-on-widget-visibility
Checklist: