Michel Weststrate

Yep, should work fine. But note that middleware that supports / reasons about asynchronous actions won't be able to process this pattern correctly. (probably no problem in most code bases)...

I really love the idea @k-g-a, especially having designated types for collections of references could greatly simplify stuff. I think synced deletes should be the default (and non configurable ?)...

Afaik it doesn't cover all / complex cases. But feel free to upgrade your TS version and give it a spint :) On Wed, Dec 11, 2019 at 10:43 AM...

> Composed and unioned sub-tree should automatically be determined via dispatcher when assigning data. I didn't entirely get the example, but yes this is how MST is supposed to work....

I think it is a pretty neat idea and is feasible. PRs welcome!

I think this is a pretty cool idea, because it would save some boilerplate around disposers.

Big question is when should those reactions be setup. afterAttach or afterCreate? AfterAttach is not always triggered (not for roots) or multiple times (when moving nodes, which is not too...

To fix the 'at what point in the lifecycle' problem, would it be fine to set up effects on the next tick? (also, minor correction on the above reasoning: side...

References map identifiers to values directly. Since you try to load lazily, you don't have a value, so you can't "resolve" the identifier. Note that we can't really support async...

Feel free to PR all three changes. Mind the `"false"` case 😊 Op di 18 feb. 2020 01:51 schreef Jay Thomas : > *Feature request* > > *Is your feature...