Timeline for Static typed Ids (integers) in C#
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 26, 2016 at 8:40 | vote | accept | Dirk Boer | ||
| Jan 24, 2016 at 15:37 | answer | added | Dmitry Nogin | timeline score: 4 | |
| Jan 23, 2016 at 4:31 | comment | added | Jeroen Vannevel | Unit tests will catch all these problems for you before compiling thus removing any lingering problems, reducing code complexity and adding code coverage. The idea you're implementing is sometimes also referred to as 'Tiny Types' and while interesting is fairly tough to maintain. It's also an added complexity when you have to map this object to your ORM layer and back (to avoid creating 2 tables for one object), etc. TL;DR: use tests to make sure you're not switching two parameters. | |
| Jan 23, 2016 at 2:06 | answer | added | svick | timeline score: 4 | |
| Jan 23, 2016 at 2:05 | comment | added | RubberDuck | +1 for good design & abstraction. It's easy to overlook creating types for this kind of thing and breaking away from Primitive Obsession. I like this very much, though many would say it's overkill. | |
| Jan 23, 2016 at 1:38 | history | edited | Jamal | CC BY-SA 3.0 |
deleted 44 characters in body
|
| Jan 23, 2016 at 1:03 | history | asked | Dirk Boer | CC BY-SA 3.0 |