Tomasz Heimowski

Following works when key is present on rendered child: ```fsharp type LazyPropsReactElement equal:'model->'model->bool key:string // added key prop } let getKey (view:'model->ReactElement) (state:'model) : string = let render = view...

What I meant when I said it doesn't work with missing key on child was it sets the `key` prop to null resulting in React warnings about non-unique keys within...

Alternatively we could add one more parameter to `lazyViewWith` so that in addition to passing `equal` function one would need to provide also `getHashCode` function or the hash itself. Even...

This works if we allow to specify `getHashCode` as function of `'model -> int option` : ```fsharp [] let deleteProp x (prop : string) = jsNative let lazyViewWith (equal:'model->'model->bool) (hash:'model->int...

I don't think we can use view hash - given the following: ```fsharp let lazyViewWith (equal:'model->'model->bool) (view:'model->ReactElement) (state:'model) = let key = (view :> obj).GetHashCode() |> string let props =...

Can you post an example? Anyway the thing is if we give such API there's a chance one might misuse it - as I did apparently :)

Even if I do it your way, `(view :> obj).GetHashCode()` returns different result on each model change for me. Is there something I'm missing about the consistent hash for `view`...

Right, the bootstrapping section could probably benefit from using dotnet SDK, which seems to be the preferred way to go now. Not really sure why the above error - mono...

Yep, thanks for reporting the issue

does setting the `homeFolder` explicitly as suggested on SO help here?