-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
fix: use stable array to prevent memoization issue in useList #7019 #7020
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
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 04a9e40 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for refine-doc-live-previews ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
The commit 43afc44 also update |
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.
Thanks for the improving Refine,
we need changeset to release this fix
Thanks for your feedback. I'll add the changeset. |
PR Checklist
Please check if your PR fulfills the following requirements:
Bugs / Features
What is the current behavior?
In commit 43afc44, the useList hook returns a new, empty array [] on every render cycle whenever queryResponse.data.data is falsy. This violates referential equality, causing hooks like useMemo and useEffect to re-calculate unnecessarily, leading to potential performance degradation.
What is the new behavior?
The useList hook now returns a stable, frozen empty array Object.freeze([]) as the default value for result.data.
fixes #7019
Notes for reviewers