Fix UseField type definition, add micro-hooks.

[johnrom]

This adds the convenience hooks from the original v3.

It doesn't add useFieldX, useSetFieldX hooks, because users should simply use useFieldMeta() and the relevant API methods from useFormikContext(). It is not going to have a noticeable performance difference. useFieldMeta provides the same functionality as using all the useFieldX() combined.

[changeset-bot]

🦋 Changeset detected

Latest commit: 00dac43

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
formik-native	Major
formik	Major
app	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

@johnrom is attempting to deploy a commit to the Formium Team on Vercel.

A member of the Team first needs to authorize it.

[dantman]

It doesn't add useFieldX, useSetFieldX hooks, because users should simply use useField(). It is not going to have a noticeable performance difference. useField provides the same functionality as using all the useFieldX() combined.

Doesn't useField declare the field? I use useFieldValue and useFieldSetValue in various places other than the field itself. e.g. A Collapse component that depends on the value of a checkbox. An effect that resets the value of a field when conditions change in a way that will make the field become invalid. etc.

[johnrom]

You can use useFieldMeta for this purpose which supplies the underlying state.

Updated my description above.

[dantman]

Ok, fine. Though this does look a lot uglier.

const { setFieldValue } = useFormikContext();
const { value: otherValue } = useFieldMeta(props.otherFieldName);

useEffect(() => {
  console.log(otherValue);
  setFieldValue(props.otherFieldName, 'foo');
}, [otherValue, setValue, props.otherFieldName]);

Than the previous v3 code:

const [otherValue, setOtherValue] = useFieldValue(props.otherFieldName);

useEffect(() => {
  console.log(otherValue);
  setOtherValue('foo');
}, [otherValue, setOtherValue]);

[johnrom]

I agree it could be more concise. The previous concise API had a reason - the smallest possible hooks were necessary to get optimized subscriptions.

This one doesn't need it, and in fact using smaller subscriptions may have a performance hit because each one is a subscription. I think a balance of this would be to return Formik API from useFieldMeta:

const [fieldMeta, api] = useFieldMeta(name);

[github-actions]

This pull request is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 60 days

[johnrom]

closed in favor of #3231