Skip to content
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

Allow load information from my component #17791

Closed
EduardoSaavedra opened this issue Jan 6, 2020 · 11 comments
Closed

Allow load information from my component #17791

EduardoSaavedra opened this issue Jan 6, 2020 · 11 comments

Comments

@EduardoSaavedra
Copy link

EduardoSaavedra commented Jan 6, 2020

Do you want to request a feature or report a bug?
Its a bug

What is the current behavior?
Im trying to watch all the properties in the tab components but it get stuck when I click in a component from my project, I´ve tried this in all my repositories and i get the same problem.

image

What is the expected behavior?
its supposed to show al the info from my component

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

React: "16.7.0",
Browser: Chrome,
OS: Apple's macOS,
And this was working the last weekend with no problem

@EduardoSaavedra EduardoSaavedra changed the title Allow load information Allow load information from my component Jan 6, 2020
@bvaughn
Copy link
Contributor

bvaughn commented Jan 7, 2020

@EduardoSaavedra There's not much I can do to help with only the info provided. Please provide a repro case (can be Code Sandbox, or a link to a website with instructions on which component I need to select) so that I can actually see the error.

This is why the new issue template says 😄

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:

@EduardoSaavedra
Copy link
Author

EduardoSaavedra commented Jan 7, 2020

@EduardoSaavedra There's not much I can do to help with only the info provided. Please provide a repro case (can be Code Sandbox, or a link to a website with instructions on which component I need to select) so that I can actually see the error.

This is why the new issue template says 😄

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:

@bvaughn This is my component I want to watch in tab component, code. What i want to see is the state of this.
and this is a GIF of what I´m doing and get only the loading
code stuck

@bvaughn
Copy link
Contributor

bvaughn commented Jan 7, 2020

The code you linked isn't runnable:

Uncaught SyntaxError: Cannot use import statement outside a module
    at run (babel.js:60802)
    at check (babel.js:60868)
    at loadScripts (babel.js:60909)
    at runScripts (babel.js:60936)
    at transformScriptTags (babel.js:324)

A gif doesn't really help me because it doesn't let me see what the runtime error in the console is.

@EduardoSaavedra
Copy link
Author

im getting this, when trying to analyse a component State, it says loading... and throw this error.

Uncaught TypeError: Cannot read property 'name' of undefined
at O (backend.js:1)
at s (backend.js:1)
at s (backend.js:1)
at s (backend.js:1)
at l (backend.js:1)
at Object.inspectElement (backend.js:6)
at t. (backend.js:6)
at t.r.emit (backend.js:6)
at backend.js:32
at t (backend.js:8)

@bvaughn
Copy link
Contributor

bvaughn commented Jan 7, 2020

@EduardoSaavedra: Can you share a way for me to run and reproduce this bug? That's what I'm looking for here 😄

Otherwise I don't know if it's been fixed by a recent PR (e.g. #17757) that hasn't yet been released to the Chrome store.

@EduardoSaavedra
Copy link
Author

Ok , im going to find the way to send you my code, so you can reproduce this bug, but I have a problem its a private repo but im trying to send the info you need. If not then im going to wait until Chrome Store release it.

thanks @bvaughn

@bvaughn
Copy link
Contributor

bvaughn commented Jan 7, 2020

You could try to install this (local) build of React DevTools to see if it still reproduces the broken behavior. (If it doesn't, then you don't need to spend any time creating a repro)

ReactDevTools.zip

If it still does, then I'd suggest trying to just rip out parts of your app until you've gotten it down to something small that still shows the bug. Then you might just be able to port that small example over to Code Sandbox and not have to worry about sharing a Git repo with me? :)

@EduardoSaavedra
Copy link
Author

@bvaughn quick question, how do i install your .zip locally?

@bvaughn
Copy link
Contributor

bvaughn commented Jan 7, 2020

  1. Download extension
  2. Double-click to extract
  3. Navigate to chrome://extensions/
  4. Enable "Developer mode"
  5. Click "LOAD UNPACKED"
  6. Select extracted extension folder (ReactDevTools)

If you already have the React DevTools extension installed, you will need to temporarily disable or remove it in order to install this prerelease build.

Install local extension

@EduardoSaavedra
Copy link
Author

Now it´s working, i Did the installation in my local, for now i am going to work with that. Thank you so much @bvaughn. Now we have to wait until Chrome release it?

@bvaughn
Copy link
Contributor

bvaughn commented Jan 7, 2020

Great! That means this was fixed by the recent PR, and will roll out to others as soon as the Chrome reviewers approve the release from a few days ago.

I'd suggest you remove the local install in a few days and get back on the main one (so you don't get left behind for future updates!) 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants