Fix #3948 - Changing state was also causing change of initial value

[DeveloperRaj]

Resolves Issue #3948

This addresses the problem of the dirty field not updating when the value of a nested object changes. The root cause of this issue is that the initialValues coming from props were directly assigned to the useRef, which did not perform a deep copy. Without a deep copy, it was modifying the original initialValues props along with the current state. Consequently, when comparing them for equality, the result was true

[changeset-bot]

🦋 Changeset detected

Latest commit: 8434aae

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

This PR includes changesets to release 2 packages

Name	Type
formik	Patch
formik-native	Patch

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]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
formik-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 10, 2024 5:56pm

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[quantizor]

@DeveloperRaj thank you, last thing can you add a unit test that verifies the initialValues object is not modified?

[DeveloperRaj]

@DeveloperRaj thank you, last thing can you add a unit test that verifies the initialValues object is not modified?

@quantizor Thanks for suggestion of test. I have added a new test that checks that initial values are not being modified when we do handleChange or setValues etc. It looks a bit messy but had no option since this bug would repro only happen when we have deeply nested objects otherwise it would work just fine even without my code change.

[quantizor]

Thanks!