[WIP] Migration from wrapper divs to Fragments #129
Merged
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.
Description
Closes #93
This PR changes unnecessary wrapper
div
s to ReactFragment
s.In React 16.2.0
Fragment
was added as name export, which is handy.But using named export requires to set react to 16.2.0 in
peerDependencies
, which may be not cool.We could leave react 16.0.0 in
peerDependencies
, but instead of importingFragment
like this:we should get it from React default export:
I'd prefer the second solution, but I would like to hear someone else's opinion ;)