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
Proxy drilling once again ... #34
Comments
WebReflection
added a commit
that referenced
this issue
Nov 20, 2023
WebReflection
added a commit
that referenced
this issue
Nov 20, 2023
WebReflection
added a commit
that referenced
this issue
Nov 20, 2023
WebReflection
added a commit
that referenced
this issue
Nov 20, 2023
WebReflection
added a commit
that referenced
this issue
Nov 20, 2023
WebReflection
added a commit
that referenced
this issue
Nov 21, 2023
WebReflection
added a commit
that referenced
this issue
Nov 21, 2023
WebReflection
added a commit
that referenced
this issue
Nov 21, 2023
WebReflection
added a commit
that referenced
this issue
Nov 21, 2023
WebReflection
added a commit
that referenced
this issue
Nov 21, 2023
WebReflection
added a commit
that referenced
this issue
Nov 21, 2023
WebReflection
added a commit
that referenced
this issue
Nov 21, 2023
WebReflection
added a commit
that referenced
this issue
Nov 21, 2023
WebReflection
added a commit
that referenced
this issue
Nov 21, 2023
WebReflection
added a commit
that referenced
this issue
Nov 22, 2023
Fix #34 - Use target type through proxy-target
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have enough of these issues caused by standards so I need to do quite some refactoring to avoid ever wrapping arrays as proxied values as it's clear that the ECMAScript people don't care and won't fix any of this:
So here the issue to target when I'll work on a coincident version that uses plain objects instead of arrays to propagate the
type, value
pair in the wild.The text was updated successfully, but these errors were encountered: