Move admin model to use & enforce nullable types throughout?
Opened this issue · 2 comments
Apart from being good practice from the point of view of the integrity of the Admin system, it would be useful to explore the idea further in the context of NOF. Have we done it on any model before?
For example, does EF make full use of this? Will it, for example, catch an inconsistency between an association being of a nullable reference type but the FK property being non-nullable, or vice versa?
The Compile Server enforces nullable types.
It's probably only a day's work to fix
Clarification: I didn't mean Student Code should do this. I meant my own Admin Model code. So it shouldn't need any change to infrastructure. I also think I'm correct in saying that nullability is a compile time feature - no different in CLR. So should not affect NOF reflector.