๐ Investigate use of Nullable Strongly Typed IDs
Opened this issue ยท 0 comments
danielmackay commented
The problem I've found is that sometimes you need to use optional/nullable foreign keys. When you do this EF Core doesn't like trying to use nullable structs for FKs. The only way I could find to fix this is to change from a record struct
to record
.
Should probably create a ticket to further investigte this and update the rule if necesary.
See usages of TeamId
for more details.
If needed update the rule - https://www.ssw.com.au/rules/do-you-use-strongly-typed-ids/