Yeah, Yeah, Yeah. There are so many issues in any framework about data passing down and up the component tree. This is so absurd and just a result of components are being forced (like a square peg in a round hole) as the big deal.
Instead, it is better to extract all logic into a FSM driven RxJS based staged graph. Why, because data-flow/control and the logic that composes it is the core of any substantial app, not components.
Once you have that components become just one of multiple types of render artifacts you can return from the logic flow. The new lit-html API is a great way to pop out dynamic components.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yeah, Yeah, Yeah. There are so many issues in any framework about data passing down and up the component tree. This is so absurd and just a result of components are being forced (like a square peg in a round hole) as the big deal.
Instead, it is better to extract all logic into a FSM driven RxJS based staged graph. Why, because data-flow/control and the logic that composes it is the core of any substantial app, not components.
Once you have that components become just one of multiple types of render artifacts you can return from the logic flow. The new lit-html API is a great way to pop out dynamic components.