Rasmus Schultz

> So is your thought that we should break down the front end spec into individual components with some guidance on component state management? Not at all :-) I don't...

@lastlink I think those issues are interesting, but unrelated and belong in a separate discussion.

There is still, to my knowledge, no demo project suite out there that requires control state. It's a bit frustrating - so many new frameworks don't support this (to any...

@Alonski we would need to think of a new feature that actually requires a component that has some sort of control state and occurs more than once. Maybe an advanced...

I do have a small date picker that I keep porting to different frameworks for testing - it's only around 50 LOC for the calendar logic... https://gist.github.com/mindplay-dk/d85fbf5427d5e4436fadc70ce46d9ac2 I would prefer...

> I was most surprised when a forgot password wasn't included in the frontends. @QuantumInformation that doesn't really present a new challenge to the frameworks though - just more of...

> there are standalone implementation of Hooks (a-la React Hooks) that can be used in any framework This gives you *state* - but it doesn't somehow give you update boundaries...

> > This gives you state - but it doesn't somehow give you update boundaries pertaining to that state. > > I am not sure what you mean by that....

>you can always build your own component concept around the minimal UI library if you need to Of course, you can always build your own library on top of another...

> It would be nice to have expandable/collapsible sections in order to challenge libraries that keep state in the components so that the validation state could be lost when the...