Ruben Bartelink

I agree in principle with pretty much all of the changes you've outlined. I think we'll be able to keep everyone happy in this repo; if necessary, the final page...

I feel the first step is to address the open issues to get to a stable state (it'll be verbose, but there won't be too many outright bad/wrong examples, and/or...

TL;DR I think we should stick to one version for now. It's not yet proven that the world needs (or anyone is pushing for) two sibling cheatsheets. ---- Depends on...

If one is looking for a practical ways to handle enums with string values without language level changes/support in the interim, TypeShape's UnionEncoder lets you (if you use a DU)...

As discussed in https://jabbr.net/#/rooms/FunctionalEventSourcing the key bit I missed is that I didnt read the stuff I typed above... The json.net native DU serialization does not emit field names. This...

I think in the jabbr you mentioned that refactoring can change the aggregate that will generate/note/emit a given event type too. The problem is I want one answer to rule...

One big thing you lose if one consolidates all the Events in the domain into one DU is that you end up visiting all the match expressions whenever you add...

Most recent thoughts (after twitter discussion and some playing in https://github.com/thinkbeforecoding/FsUno.Prod/pull/8 ) are that now `Game` has: ``` type Event = | GameStarted of GameStartedEvent | CardPlayed of CardPlayedEvent |...

Implemented DU body emission high level concept as mentioned in previous comment [in FunDomain](https://github.com/bartelink/FunDomain/commit/e9082ed4c14ca911df6a381017a54b0a203078ac)

[Complete impl of the concept pushed to FunDomain](https://github.com/bartelink/FunDomain/commit/4a519a27cffc7229538b9b499b22aed3a0e46797). @thinkbeforecoding Raises the questions: 1. is this something you're interested in using in FsUno.Prod as a replacement for the existing case name...