-
-
Notifications
You must be signed in to change notification settings - Fork 454
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) - make all components in examples have displayNames in devtools #330
Conversation
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.
Nice! Thank you for having a look at that. It’ll be very important once people start testing the devtools we’ll be releasing soon
Hmm, sailci seems to be stuck. Looking forward to the devtools ^^ |
@JoviDeCroock all the integrity checks on our yarn.lock files are deleted. Are you trying to hack us? Just kidding - but can you exclude those lock file changes from the PR and I'll get the rest merged today 👌 |
@andyrichardson I really don’t know why that happened, I’ll update yarn and revert the change. Sorry for the inconvenience, I’ll have time this weekend not at my pc this week. No problem if you want to do this. |
@JoviDeCroock @andyrichardson going to merge this along with #348 to clean up our PR tab a little! Looks like all integrity hashes were returned and the changes otherwise look really good to me! |
When exploring your devtools I noticed that there were a lot of places where the component would be labelled as
<Unknown>
in the React devtools. This fixes this issue for the examples.It also cleans out some stale deps and subdeps from the
yarn.lock
files.