- From: James Browning <notifications@github.com>
- Date: Mon, 15 Jul 2019 23:12:56 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 16 July 2019 06:13:18 UTC
> Could that be put inside of something like customElements instead? Nope, unlike previous iterations of decorators in the current proposal decorators are not values, they're a separate namespace thing all together. The consequence of this is all decorators need to either be global or put into a module. The motivation behind this is previous iterations of the decorator proposal basically weren't very useful for engines (or tools) to optimize as they couldn't be statically analyzed, by having all decorators known ahead of time engines (and tools) can do stuff ahead of time as well. -- 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/823#issuecomment-511680104
Received on Tuesday, 16 July 2019 06:13:18 UTC