[WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099)

justinfagnani created an issue (WICG/webcomponents#1099)

As mentioned in https://github.com/WICG/webcomponents/issues/1009, I think we really need to have written use cases that detail what exact set of capabilities are needed to meet them.

Some questions we should answer for any given use case:
- Is it required that the solution run with without script turned off? Why?
- How are components loaded?
- Can the templates be static, or do they have interpolations?
- Do templates require control flow?
- Do template expressions need to be able to transform data? In what ways?
- Do expressions need to be able to call out to JavaScript?
- What percentage of elements within a set (design system, app, etc) need to be implementable with this capability set to be useful?
- What percentage of most element definitions need to be "declarative"? Can any imperative extensions run during first render?
- Do other components and libraries need to import the declarative definitions? How?

Describing how these things work, end-to-end with respect to a specific set of _capabilities_ (not syntax) will help show that a proposed set of capabilities actually meets a use case.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1099
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1099@github.com>