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: open/close animation on personal dashboard is choppy #9253

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

thomasheartman
Copy link
Contributor

@thomasheartman thomasheartman commented Feb 7, 2025

Extracts each panel into its own component for the personal dashboard. This lets us use separate states for each panel, which in turn lets each panel change its open / close state without causing the other panels to re-render.

When you have a lot of flags and/or projects, the list to render becomes very long, which causes performance problems, especially when you need to rerender both flags and projects and the timeline whenever one of them changes.

The problems were especially noticeable in Firefox for me. Even with this, the event timeline is a little choppy. I suspect that's because of it might take a long time to paint? But we can look into that later.

Also updates the dashboard state hook to let you only pass in the flags/projects you want. We could extract this into three different hooks that all use the same localhost key, but I'm not sure whether that's better or worse 🤷🏼

Copy link

vercel bot commented Feb 7, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
unleash-monorepo-frontend ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 7, 2025 10:25am
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
unleash-docs ⬜️ Ignored (Inspect) Visit Preview Feb 7, 2025 10:25am

Copy link
Contributor

github-actions bot commented Feb 7, 2025

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Files

Comment on lines +41 to +45
props?.flags?.length &&
(!state.activeFlag ||
!props.flags.some(
(flag) => flag.name === state.activeFlag?.name,
))
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I took these out of variables because the linter didn't recognize props.flags as definitely being there if the variable was true. So to avoid using !, I put it in there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: New
Development

Successfully merging this pull request may close these issues.

1 participant