[WICG/webcomponents] A components framework based on <template> (Issue #1077)

I recently released a framework I’ve been working on - that implements a lot of what is described in this proposal (which I only encountered just now)

https://github.com/yuval-a/Sprout

Mine has a “development environment” and a “compiler script”
But the “compiled version” does use <template> elements to encapsulate components logic.

The framework rely on what it calls “State Attributes” - attributes on elements inside the component template with values starting with a $ - the runtime creates a binding between the attribute node values of a “rendered” component elements and the values in a State object thus enabling “state management” and “reactivity”

A “rendered” element is a custom element, and the runtime logic is a “ReactiveElement” class that extends HTMLElement classes -  adding and handling those features.

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

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