-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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 debug tests #3980
base: v11-linked-list-prev-index-nextDom-2
Are you sure you want to change the base?
Fix debug tests #3980
Conversation
📊 Tachometer Benchmark ResultsSummaryduration
usedJSHeapSize
Results02_replace1k
duration
usedJSHeapSize
run-warmup-0
run-warmup-1
run-warmup-2
run-final
03_update10th1k_x16
duration
usedJSHeapSize
07_create10k
duration
usedJSHeapSize
filter_list
duration
usedJSHeapSize
hydrate1k
duration
usedJSHeapSize
many_updates
duration
usedJSHeapSize
text_update
duration
usedJSHeapSize
todo
duration
usedJSHeapSize
|
Size Change: +37 B (0%) Total Size: 38 kB
ℹ️ View Unchanged
|
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 looking into this!
vnode == null || | ||
vnode === true || | ||
vnode === false || | ||
typeof vnode === 'function' |
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.
Should we do this typeof once and reuse it's result here and line 249?
Same for patch
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.
Just checked and storing the result in a variable is 10b larger. I think for now it's fine to leave it as is.
This PR fixes the debug tests and a few compat ones. Got the total failure count down to 5. The remaining failures are all for
forwardRef
and it seems like we're puttingref
back in props at different stages for vnodes vs internals. Haven't found out why though, but I think the existing fixes are already worth PR'ing.