Customizer now uses React 16 context. (#5701) #6268
Merged
Conversation
This file contains 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
* Moving Customizer to new React context.j * adding change files. * reversing change. * Update package.json * Fixing merge issue. * Dropdown fixes. * Fixes for foundation. * Oops * adding changes.
cliffkoh
approved these changes
Sep 7, 2018
2 tasks
JasonGore
added a commit
that referenced
this pull request
Sep 7, 2018
* Remove Object.assign usage inadvertently added by #6268. * Change file.
9 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Pull request checklist
$ npm run changeDescription of changes
Now that Layer uses React Portals (#6211), we can reintroduce React 16 Context (#5701) and not have it break Layered content (#6055).
Focus areas to test
Microsoft Reviewers: Open in CodeFlow