-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: update implementation of getReactFiberFromNode to be compatible with React 17 #16392
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 020a5e1:
|
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Perf comparison
Perf tests with no regressions
|
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: 5feec8dc74dd5db94341c69ca9254e8af210488e (build) |
} | ||
} | ||
|
||
throw new Error('getReactFiber(): Failed to find a React Fiber on a node'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: consider having a test case for the throw
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added 👍
…ix/popper-warning � Conflicts: � packages/fluentui/CHANGELOG.md
Which version of |
Fixes #16192.
In React 17 internal keys were changed (facebook/react#18377), I performed a small refactor to extract shared code (
Popper
andFiberNavigator
) to a single place and added unit tests. Also manually tested with React 17.