-
Notifications
You must be signed in to change notification settings - Fork 435
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: restore support for defaultOrdering. #7626
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
No changes to documentation |
Component Testing Report Updated Oct 17, 2024 12:30 PM (UTC) ✅ All Tests Passed -- expand for details
|
⚡️ Editor Performance ReportUpdated Thu, 17 Oct 2024 12:33:34 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
working as expected, thanks!
* next: chore(deps): update dependency sanity-diff-patch to v4 (#7630) feat: validate PR title against conventional commits (#7580) chore(deps): update dependency @sanity/tsdoc to v1.0.113 (#7627) fix(deps): update dependency @sanity/client to ^6.22.2 (#7625) chore(deps): update typescript-tooling (#7605) fix: restore support for defaultOrdering. (#7626)
fixes #7586
Description
#7554 broke default sorting because
useStructureToolSetting
always returnednull
from localStorage synchronously, therefore overriding the passed defaultValue. This fixes the issue by always falling back to the defaultValue whenever the settings store emitsnull
.What to review
Does it make sense?
Testing
Ideally
useStructureToolSetting
should have unit tests, but I'm not able to prioritize spending time on that right now.I've manually tested and verified that the behavior is as intended.
Notes for release