Add support for Fragments in Head #3502
Merged
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
Contributor
|
Thanks. Can we have a test case for this? |
Contributor
Author
|
Currently canary targets |
Contributor
|
@Sekhmet you've checked for |
Sekhmet
force-pushed
the
head-fragments
branch
from
16cbb18 to
9f3babd
Compare
arunoda
approved these changes
Dec 28, 2017
Contributor
arunoda
left a comment
arunoda
left a comment
There was a problem hiding this comment.
This looks really great.
|
🙏 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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 PR adds support for React Fragments (16.2.0) in
<Head />.Fixes #3399.