You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In multiple situations forwarding props {...rest} through 2 components broke certain behaviours.
I reproduced a case where bind:ref in the outermost parent component stopped working as soon as I used props forwarding via ...rest. It was working fine with 5.0.0-next.17 but stopped working after upgrading to 5.0.0-next.26.
I'd say this is expected behavior. Spreading works one way, not two-way (I'm suprised this worked at some point). To fix it, use bind:ref in the middle child explicitly - although there's an infinite loop when $inspect is commented in, which is why I'm keeping this issue open.
Describe the bug
In multiple situations forwarding props {...rest} through 2 components broke certain behaviours.
I reproduced a case where bind:ref in the outermost parent component stopped working as soon as I used props forwarding via ...rest. It was working fine with 5.0.0-next.17 but stopped working after upgrading to 5.0.0-next.26.
Reproduction
See this REPL
Logs
No response
System Info
Severity
blocking an upgrade
The text was updated successfully, but these errors were encountered: