I think I'm on to something now: declarative custom element creation w/ template literals.https://github.com/mikeal/gza
Show this thread
-
if you have an element that needs to hold state, you shouldn't be creating it in the dynamic templating.
What would you propose as an alternative? Currently "component" almost always refers to "stateful DOM thing" – it'd be neat if it was poss.
-
-
Also want to re-emphasize that I'm really digging this direction – a future where there's less custom code than with Nanocomponent is good!
-
Ya, there's a lot going on, I'll need to write up something a bit more detailed. But I think these "lifecycle" events may be an anti-pattern
End of conversation
New conversation -
-
-
Ya, I think this might be what is making the programming so complicated though. You have two very different use case slammed into each other
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.