Bnaya Peretz

I think that it's out of scope for root cause to set these things for the user, and spawning pages for him. But we do want to support showing data...

This is because there's attach call and testEnd calls, so result folder is create for the test under that run. We can in some point ignore if there are 0...

The optimal solution from that would be to generate unique test name using jest's mechanism, for example: ``` it.each([ ['a', 1], ['b', 2], ])('%s %p Should add 4 todos', ```...

See my PR, https://github.com/skokenes/mst-typescript-dec-test/pull/1/files Using that pattern is verbose, but better than hand-writing specific interfaces ```ts const ModelAInferred = t.model({ foo: t.string }); type ModelAFactoryType = typeof ModelAInferred; interface ModelAFactoryInterface...

Output types, only one IModelType is emitted per created model factory ```ts import { IModelType, Instance, _NotCustomized, ISimpleType } from "mobx-state-tree"; declare const ModelAInferred: IModelType; declare type ModelAFactoryType = typeof...

I got to these kind of pattens a while ago when nested models killed my IDE. I've noticed that when you hover a variable with interface type, you see the...

union inferring internal stuff regarding the model factory, what leads to that behaviour. I believe that if the type that passed to the types.model() would be "named typed" and not...

> but my models include flows which don't work for me when compiling to JS and importing into another library. I get a "Action requires parent context" error for any...

Interesting! I will try to look into that aswell

I think i have a nice solution, but i need help with validation before we can make it into a PR basically i'm wrapping types.union calls with a function that...