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
bug #943 [LiveComponent] Working around issue where FormView is passed to the component (weaverryan)
This PR was squashed before being merged into the 2.x branch.
Discussion
----------
[LiveComponent] Working around issue where FormView is passed to the component
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| Tickets | Conversation with `@1ed` on Slack
| License | MIT
In this case, the FormView will likely be initialized with certain data and, in the case of something like a CollectionType, it will have certain children fields. If we try to get the "form instance", that will be created "fresh" with different data and different fields, which causes the "compound" check to fail.
Getting the "compound" from the form instance was always a workaround for autocomplete, which tricks us by changing their compound flag. This goes back to the original logic, with a workaround for autocomplete.
Cheers!
Commits
-------
67bc0ea [LiveComponent] Working around issue where FormView is passed to the component
0 commit comments