Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562)

> I know its a property change. And you have shown yet another way to handle it. More diversity is just what is the problem in this case. 

But it's the only way, right? Frameworks are just setting up setters under-the-hood. You *might* be able to set up a Proxy in the constructor if you need to observe unknown property changes.

Frameworks are going to give you best practices, that's what they're for. I personally think web component specs should remain fairly low-level and leave opinions to developers to iterate on. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/562#issuecomment-245015793