Kyle Gray

Since the underlying library is using the legacy context api. There are a few re-renders that do occur when any update to the input is happening. Possbile duplicate of #14

Alternatively @TheSharpieOne I was also thinking about making an update to allow the user to pass in a `name` prop on the `AvFeedback` and then rendering that field's error message...

Currently this library is using the legacy context api and there aren't any solid docs on this at the moment. We have a planned re-write to the new context api...

There is no PR open for this yet but we are migrating to the latest version with hooks. If you want to fix this warning for older versions feel free...

The `model` prop is only for initial values and is not for the whole state. If you want to manage the `value` prop yourself pass it to the input itself

Try installing the latest version. Possibly fixed via #144

Could you maybe post a quick codesandbox of that? We have a similar [feedback component](https://availity.github.io/availity-react/components/feedback/feedback/) in our react mono repo that does that but we recently switched to one of...

Check out our Upload component and how we wrote it. https://github.com/Availity/availity-react/tree/master/packages/upload Essentially we create the `CustomInput` tag and hide it from the DOM. Then we create our own button that...

Maybe this will help you out a little bit: https://codesandbox.io/s/availity-custominput-file-qxjix You can't control the state of the file input so you can fake it like we do.

Feel free to submit a PR or migrate to one of our newer form libs on a different validation framework. [Availity Form](https://availity.github.io/availity-react/form/)