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
@lgrapenthin I wasn't aware that :ref also takes a fn. Looks like they also plan to deprecate the use of strings as a :ref value. At the moment it is not possible to avoid wrap-form-element.
wrap-form-element is copied over from om to make sure controlled inputs behave properly. I think we had problems with input fields loosing state like the cursor position. But to be honest I can't remember the exact details anymore :)
I think a fix for your issue could be to pass the :ref in wrap-form-element down to the actual input element. Patch with test welcome!
A fn passed as :ref is not invoked with the DOM element but the component class instance.
Is there a way to avoid
wrap-form-element
, probably via a metadata hint? Also I'd be curious to know what the purpose of wrap-form-element is.https://facebook.github.io/react/docs/more-about-refs.html#the-ref-callback-attribute
The text was updated successfully, but these errors were encountered: