You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This library is amazing, and I'm going to use it for my next project. However, reading through docs and code, I found that it uses Proxy to observe property changes. I wonder why Proxy? I know proxies as quite slow and clunky solution which is barely polyfillable.
Why not use the explicit list of allowed properties, like it is done for attributes? It could look like the following:
This not only removes the need in Proxy at all but also gives us a clearer and more explicit API of the component that can be easily found in source code. It may also solve #168.
The text was updated successfully, but these errors were encountered:
This library is amazing, and I'm going to use it for my next project. However, reading through docs and code, I found that it uses Proxy to observe property changes. I wonder why Proxy? I know proxies as quite slow and clunky solution which is barely polyfillable.
Why not use the explicit list of allowed properties, like it is done for attributes? It could look like the following:
This not only removes the need in Proxy at all but also gives us a clearer and more explicit API of the component that can be easily found in source code. It may also solve #168.
The text was updated successfully, but these errors were encountered: