We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
Why are you changing the Fragment key each time there is a reset?
In render of Field we have this:
field-form/src/Field.tsx
Line 644 in e918484
This is causing unwanted unmount/remount of the Field each time we reset the form.
I don't see the point of doing that, but maybe I'm missing something. Can you help me understand?
The text was updated successfully, but these errors were encountered:
Hi, Why are you changing the Fragment key each time there is a reset? In render of Field we have this: field-form/src/Field.tsx Line 644 in e918484 return <React.Fragment key={resetCount}>{returnChildNode}</React.Fragment>; This is causing unwanted unmount/remount of the Field each time we reset the form. I don't see the point of doing that, but maybe I'm missing something. Can you help me understand?
Hello, the reason for this forced update is the current node being cleared
This action is necessary to ensure that the field will be updated even if it has been memoized or cached.
Sorry, something went wrong.
No branches or pull requests
Hi,
Why are you changing the Fragment key each time there is a reset?
In render of Field we have this:
field-form/src/Field.tsx
Line 644 in e918484
This is causing unwanted unmount/remount of the Field each time we reset the form.
I don't see the point of doing that, but maybe I'm missing something. Can you help me understand?
The text was updated successfully, but these errors were encountered: