chrisdibble / feform Goto Github PK

Hey Chris. I'm having some issues that I think may be caused by the library using some deprecated React features. I'll see if I can come up with a simple test project that duplicates the issue, but what I'm seeing is that after I include a Form component on a page, any component that comes after the Form in the DOM doesn't respond to click events.

I'm not positive where the problem is coming from, but I"m wondering if it can be due to these issues:

1. The project depends on React.PropTypes, which is deprecated in React 15 and will go away in React 16. This needs to be replaced by the new prop-types module.

2. Also, it looks like there is a dependency on the old refs attribute, which has been replaced by a ref callback.

I'm not sure if the second issue is related to the problem I'm seeing or not.

Any chance you'd be able to look into this in the near future?

In some cases, such as when you have a form for a PATCH request, it makes sense to only validate the fields that aren't pristine (since these are the only ones we care about in these situations).

feform should have a property that, when set, causes validations to run for fields that aren't pristine.