fix(Forms;SideNav;TreeView): Make React.Children null safe #535
Conversation
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
|
Deploy preview for fundamental-react ready! Built with commit ad1b676 |
greg-a-smith
changed the title
Contributor
|
@skvale can you update this PR? We split our tests up so there are some conflicts, but changes should be pretty simple. Thank you! |
This prevents cloneElement throwing an error when a child is null.
Contributor
Author
|
@hertweckhr1 I just rebased onto master 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
This prevents cloneElement throwing an error when a child is null, such as with
Description
React.isValidElementchecks, but I changed it to be consistent.fixes #523