The design of the Incident entity varies across JasperFx projects

[mrs01dev]

There are different design patterns for the Incident entity within JasperFx repositories. Specifically, the 'CritterStackHelpDesk' project defines Incident as a public record, while the 'IncidentService' sample uses a public class for the same use case."

When utilizing JasperFx wolverine ,Please, elaborate on the significant tactical DDD design differences between defining an entity as a public record (as in CritterStackHelpDesk) versus a public class (as in IncidentService)? Furthermore, which design pattern is considered superior for this use case?

[jeremydmiller]

@mrs01dev Please use Discord or Discussions for questions. And you'll want to ask that in a different venue anyway because I don't have strong opinions about what you just asked and certainly not about DDD things:)

My mere opinion and why you see some differences from the original Incident I copied from Oskar is that records become ugly to work with in code when there's more than a handful of properties. Simply preference.

[mrs01dev]

Thank you for the clarification.