Skip to content

Devtools component incspector not intractable if component has a Proxy in data #708

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

Closed
spzm opened this issue Jul 21, 2018 · 1 comment
Closed
Labels
bug need team repro We acknowledged your report and will soon try to reproduce it

Comments

@spzm
Copy link
Contributor

spzm commented Jul 21, 2018

Version

4.1.4

Browser and OS info

maxOS, Chrome 67

Steps to reproduce

Create a property/data/... (any data that inpected by devtools) as a Proxy:

new Proxy(function() {}, {get () { return new Proxy(function() {}, {})} })

Then inspect the element. Devtools won't able to show any data and throw the error:

Uncaught TypeError: t.match is not a function

image

What is expected?

The inspected elements show the properties, data, ...

What is actually happening?

I just copy description from #499 (because the result is the same):

No content is appeared at right side, when I click on a component to inspect it.
After I click on a component to inspect it, there are also a lot of errors in my console.


Looks related to #499 issue.
As I understand, previously Proxy was removed from vee-validate in this commit to resolve the issue.

@Akryum Akryum added bug need team repro We acknowledged your report and will soon try to reproduce it labels Jul 25, 2018
@spzm
Copy link
Contributor Author

spzm commented Jul 26, 2018

Hi @Akryum, I created a repo with example and github-pages (try to inspect App or HelloWorld component). I hope it will help with reproducing the issue.

image

@spzm spzm changed the title Devtools component inceptor not intractable if component has a Proxy in data Devtools component incspector not intractable if component has a Proxy in data Jul 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug need team repro We acknowledged your report and will soon try to reproduce it
Projects
None yet
Development

No branches or pull requests

2 participants