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(desk-tool): force re-renders on user components on navigation #2868

Merged
merged 1 commit into from
Oct 18, 2021

Conversation

ricokahler
Copy link
Contributor

Description

The performance improvements of the desk-tool preserves the instance of the existing child component. For certain edge cases, this behavior is not desired and is unexpected.

This change forces user-defined components to render on pane navigation changes.

Notes for release

Fixes an edge case for user-defined components. All user-defined components are re-rendered on navigation regardless if the structure child is a function or not.

@vercel
Copy link

vercel bot commented Oct 15, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.

perf-studio – ./

🔍 Inspect: https://vercel.com/sanity-io/perf-studio/DCHNHidBow1KbaKS497AzuSyNNuk
✅ Preview: https://perf-studio-git-fix-force-user-component-rerender.sanity.build

test-studio – ./

🔍 Inspect: https://vercel.com/sanity-io/test-studio/94DBs7A6xCzsaSKfXQmDTznAjRfs
✅ Preview: https://test-studio-git-fix-force-user-component-rerender.sanity.build

studio-workshop – ./dev/workshop

🔍 Inspect: https://vercel.com/sanity-io/studio-workshop/Gf5vR9UuB441k3PLaFtGa1wrhRz1
✅ Preview: https://studio-workshop-git-fix-force-user-component-rerender.sanity.build

@ricokahler ricokahler merged commit d8bd508 into next Oct 18, 2021
@ricokahler ricokahler deleted the fix/force-user-component-rerender branch October 18, 2021 13:23
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.

None yet

2 participants