This #3862 caused this problem.

But I think you can make your component safer and clearer. like this

const CustomInput = ({propsA, propsB}) => { return ( <div> <input type="text" className="composed-component-classname"   propsA={propsA}  propsB={propsB}/> </div> ); };

Probably you have written props type to make your code look clearer, but either way {...props} is not a safe style of writing, because if Formik add a type props one day, it will break your code

The above is an example for simplicity.. not actual code.

1 - A breaking change should not be put into a minor release.
2 - Spread props are explicitly intended to work exactly like the above example. The lib should have a clear API - as consumers of the library may have many different use cases. There is no reason to add "type" or "className" as they were already covered by the spread ...rest props.

The above is an example for simplicity.. not actual code.

1 - A breaking change should not be put into a minor release. 2 - Spread props are explicitly intended to work exactly like the above example. The lib should have a clear API - as consumers of the library may have many different use cases. There is no reason to add "type" or "className" as they were already covered by the spread ...rest props.

Understood, I know that's a breaking change. But I mean you can do this to improve your code health, Anyway, it's just my personal thought. if you don't like it, I'm sorry bro, You can ignore it.

FWIW it also breaks our code (specifically field validation, where for complex fields we add the is-invalid class), because the referenced PR now explicitly passes className=undefined 😮 in the remaining props in the case there's no className…
My vote is on reverting this PR.

Also hit us. Happy we caught this with snapshottests before going live.

My suggestion is also to revert this

This is a issue for us, especially with using tailwind. Surprised this made it into a stable minor release, I imagine this effects a lot of people.

Also, if anyone else is wondering, this actually broke for me in 2.4.3, not 2.4.4