Fix useFormState and useField Flow types #630
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The exported flow typing in index.js.flow doesn't match what's actually used in
useFormState
. When using this externally, this causes Flow to think thatuseFormState
might returnnull
orundefined
, when that appears not to be the case. It also thinks that the params are required when they're really optional.src/index.js.flow
src/useFormState.js
It looks like a similar change was made in #486 to fix the TypeScript typings in the same way.
typescript/index.d.ts
I'm using this locally with
npm link
and it's working for me. I would add// @flow
touseFormState.test.js
and then import from./index
instead of./useFormState
, but it seems flow and jest aren't working together out of the box.