Tyson Williams

> - Logs displaying messages, state, and state diffs The logging of those three things should occur in Elmish instead of Elmish.WPF since they are independent of WPF, right @cmeeren?...

Ok, I understand now. Thanks for your explanation @cmeeren. I created the issue I promised about my ideas to improve logging. It is issue #105. I think about logging as...

That makes sense. I am open other ways to handle validation errors. I am interested to see the proposed change.

The user is free to expose "errors" (just like any other data) via a `OneWaySeq` or `SubModelSeq` binding. I have not thought very hard about the tradeoffs between the current/`INotifayDataErrorInfo`...

In the suggested / proposed change is, would Elmish.WPF continue to use [`INotifyDataErrorInfo`](https://docs.microsoft.com/en-us/dotnet/api/system.componentmodel.inotifydataerrorinfo) or stop using it?

@xperiandri, the animation I saw in UWP with addition/removal from an `ObservableCollection` looked great. I assume that this requires the more complicated keyed merge (aka a merge that uses IDs)....

Yes, that would be preferred. Maybe you could record the animation for both algorithms so that the difference is clear to us.

I merged the previous PR using FastHub with merge type "rebase". I see this merged a commit with a different hash. The other options were "merge" and "squash". I think...

I don't see a way to drop the previous commit via the GitHub website. Can you do that and push the resulting branch?

I think you accidentally added a second commit to the branch in this PR