A resource route maps a number of related requests to actions in a single controller.

Personally, I rather like the idea of typing into a field, backspacing to undo what you just typed, and having the field (and form) go back to being pristine. Aside from that aesthetic difference, my definition has the practical implication that it lets you know if you need to save the record or not.

And I'm all for not adding a gazillion flags to to an elegant library.

Without elegant ways of expressing loops/iterators (like angular does with directives), the primary way to keep JSX readable thus becomes copying and pasting.

But this is starting to become rather verbose at what could be a much simpler and more elegant solution if only there were another template helper that could do variable assignment.

Like they tried so hard to make things easy they didn't care that they weren't elegant or simple.

Here's a proxy store I wrote to derive the value of a store nested within other stores, it plays nice with typescript and can go infinitely deep

Just ran into this problem myself and will work around it less elegantly for now.

This is the most elegant.

More elegant, just for fun: const parents = node => (node.parentElement ? parents(node.parentElement) : []).concat([node]);