Using strongly-typed entity IDs to avoid primitive obsession (Part 2)

added by DotNetKicks
4/11/2019 11:09:27 AM

2 Kicks, 253 Views

In my previous post, I described a common problem in which primitive arguments (e.g. System.Guid or string) are passed in the wrong order to a method, resulting in bugs. This problem is a symptom of primitive obsession; using primitive types to represent higher-level concepts.