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

added by DotNetKicks
4/16/2019 10:19:17 AM

2 Kicks, 213 Views

In a 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.