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

Do not use Proxy Api #42

Closed
JoTrdl opened this issue Oct 18, 2016 · 1 comment
Closed

Do not use Proxy Api #42

JoTrdl opened this issue Oct 18, 2016 · 1 comment
Labels
✨ enhancement a "nice to have" feature

Comments

@JoTrdl
Copy link
Contributor

JoTrdl commented Oct 18, 2016

Hello,

First, thanks a lot for your lib, really good work.

But I have one complaint: do not use Proxy() because it is impossible to polyfill it. A good description of the problem can be found here: http://stackoverflow.com/questions/24907229/is-there-proxy-object-polyfill-available-google-chrome

It is possible to polyfill Proxy() for an object that already contains properties but impossible to detect new added props and call the handler.
In the Google Proxy-polyfill source, it is quite clear: https://github.com/GoogleChrome/proxy-polyfill/blob/master/proxy.js#L160

Thanks.

@logaretm
Copy link
Owner

logaretm commented Oct 18, 2016

I didn't want to use it, and I'm trying to ditch it. but I needed some way to prevent the render errors since the properties and fields objects are not available until the directive is being bound. I wanted something like PHP's magic __get, but I couldn't find something similar other than the proxy object.

If you have a suggestion how to achieve this it would be great, and I will be more than happy to get rid of the proxy objects. until then I'm afraid I have to use them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ enhancement a "nice to have" feature
Projects
None yet
Development

No branches or pull requests

2 participants