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
Going to try to open a PR for this, but wanted to bring it up in an issue first. findDOMNode is deprecated in favor of refs. I think the safest way to fix this would be to create a single ref that is used in one of two ways:
When using a render prop, pass the ref into the render prop function and require the developer to pass it down to their input (I believe there is precedence for this in other libraries, but need to verify that...)
When not using a render prop, pass the ref straight to the default input that is controlled directly by the input mask component.
I'm going to try this and see what it does to the tests. If it works out, I'll open a PR for it, unless I hear objections here.
The text was updated successfully, but these errors were encountered:
Need this feature to. Im using react-input-mask with react-datepicker and datepicker passes own onFocus handler to input. But my custom input wrapped inside with <div>, so I need input ref to handle focus properly.
If I get ref as suggested in closed issues: ref={ref => this.input = findDOMNode(ref)}
I get next eslint warns:
So it don`t feels like clean solution
Going to try to open a PR for this, but wanted to bring it up in an issue first.
findDOMNode
is deprecated in favor of refs. I think the safest way to fix this would be to create a single ref that is used in one of two ways:input
that is controlled directly by the input mask component.I'm going to try this and see what it does to the tests. If it works out, I'll open a PR for it, unless I hear objections here.
The text was updated successfully, but these errors were encountered: