Michel Weststrate

In principle the point of Immer is to "modify" immutable properties, so I think I'm missing the problem you're running into here. Also it seems that you are hiding the...

recipes should not use a default argument, as they are never seen by `produce`. `produce` would indeed in such a case indeed return undefined, so the inferred type is correct.

all es5 should be valid es6 I'd expect. Please create a small repository that demonstrates the problem.

A risk might be performance, previously, all values in MST were backed by the general concept of 'node' that took care of all the householding around values. This was split...

Really like where this is going. Not sure about the 'best' api yet. A consideration: I think hooks and actions quite often want to close over the same state, so...

@k-g-a I think it is a really good idea. Especially because we can introduce it gradually by introducing as experimental type first as you suggested. As far as I know...

Sorry, could you summarize it without referring to an entire thread? Note that in MST there is no code generation unlike in mst-gql, so the options are a bit more...

Initial reaction: like! Although it is kinda set it does leak the normalization abstraction. Just a random idea, didn't think it through, what if we would keep things as is,...

I think it would be great if @xaviergonz suggestion was implemented: ``` asRef(owner, propertyName) => { readonly valid: boolean, // true if the ref is not broken, false if it...

@Amareis those can already be implemented using custom refs.