I've been playing around with the next "React killer", demonstrating my assertion that @finalformjs can adapt to any future frontend framework.
What do you think?
https://t.co/zFbjQ7JPGW
Published the first public version of effector-final-form. These are @EffectorJS bindings to @finalformjs. The library allows you to work with forms via @EffectorJS operators.
https://t.co/XcYKgtAzc9
What if a form library were so framework agnostic that it could provide value to not-yet-invented frontend frameworks? Or the new hotness, @solid_js.
https://t.co/5WVSoaQhFv
@ryanflorence This is the future I planned for when designing @finalformjs. As long as the #ReactKiller is running JS, FF is ready to manage its client-side form data.
It's not often that a bug is discovered in π Final Form, but when it is, it's usually around async validation.
Async errors were being cleared when the next async validation was started. See demo: https://t.co/zIBRQHq8ln
And the new React docs have a form example withβ¦
π₯π₯π₯π₯π₯π₯π₯π₯
β¦a single input!!
https://t.co/AhOIe7i0Y0
Are you building an app with more than one input? Try React @finalformjs.