Fix Flow typings for UseFieldConfig and FieldProps

[eugene-stativka]

There was a mismatch between the source code and Flow typings which led to the following error:

<Field
  name={name}
  component={SomeCustomInputComponent}
  /* ^^^ Flow error here:
  Cannot create Field element because in property component:
   • Either function [1] is incompatible with string literal
     input [2].
   • Or function [1] is incompatible with string literal
     select [3].
   • Or function [1] is incompatible with string literal
     textarea [4].
  */
/>

[codecov]

Codecov Report

Merging #503 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #503   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          14     14           
  Lines         231    231           
  Branches       57     57           
=====================================
  Hits          231    231

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 13008e3...4629353. Read the comment docs.

[erikras]

I feel like ignoring SupportedInputs is a mistake. Seems like an important shortlist of valid strings.

[eugene-stativka]

I feel like ignoring SupportedInputs is a mistake. Seems like an important shortlist of valid strings.

I am not sure I understood where SupportedInputs are ignored.

component?: $PropertyType<RenderableProps<*>, 'component'>, 
// ^^^ this is the same as:
component?: React.ComponentType<*> | SupportedInputs

Please clarify.

[erikras]

Oh, shit. I didn't know you could do that. 👍

[erikras]

Published in v6.0.1.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.