test: add unit tests for unsetEmptyArray behavior#12939
Closed
kamja44 wants to merge 1 commit intoreact-hook-form:masterfrom
Closed
test: add unit tests for unsetEmptyArray behavior#12939kamja44 wants to merge 1 commit intoreact-hook-form:masterfrom
kamja44 wants to merge 1 commit intoreact-hook-form:masterfrom
Conversation
Member
|
could you please combine all your prs into one? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds unit tests for the
unsetEmptyArrayutility function, which unsets a given path in an object if the value is an empty array (or falsy after compaction).unset()is called when the target value is an empty arrayunset()is not called when the array has truthy elementsunset()using Jest and verifies call behaviorThis function is used internally to clean up empty values in form-related objects like
errorsordirtyFields.Having test coverage ensures correct conditional cleanup and improves confidence in future refactors.