Dataviews: remove unneeded ref callbacks#77179
Conversation
manzoorwanijk
left a comment
There was a problem hiding this comment.
It's weird that we had to do that in the first place. Thank you for the cleanup.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Size Change: -146 B (0%) Total Size: 7.74 MB 📦 View Changed
ℹ️ View Unchanged
|
b9bc1e2 to
d1677a2
Compare
|
Flaky tests detected in d1677a2. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/24187458999
|
Spinoff from ESLint upgrade in #76654 where there is a new error detected (from the
react-compilerplugin, false positive) when assigning refs in thesetElementReffunction.It turns out that these functions can be removed completely and we can pass the
refobject directly to theComposite.Itemcomponent. All we need is to fixup the type of theuseRefcall. That was probably the original reason for adding the callback -- a type error.