[DO NOT MERGE] Replay React Devtools fork preview - #15
Draft
markerikson wants to merge 2 commits into
Draft
Conversation
markerikson
force-pushed
the
replay-react-devtools
branch
from
July 1, 2024 20:24
6597f4d to
849217d
Compare
* Fix Flow issues in Replay RDT fork * Fix outstanding lint issues
|
Probably easier to rebase (going forward) if we squash our changes into a single commit. (Otherwise you might end up resolving conflicts multiple times.) |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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 displays the full changes between our ongoing custom fork of the React DevTools for use inside of Replay, purely for easy visibility.
It supersedes PR #2 , which had multiple merges down from React
mainover time.This PR instead will be rebased monthly so that we stay up to date.