This may be common knowledge but I’ve never seen it online.
[] public Entity Entity { get; set; }
You now get a warning when accessing without a check and when setting to null.
Sadly you still need to ! in quries
This may be common knowledge but I’ve never seen it online.
[] public Entity Entity { get; set; }
You now get a warning when accessing without a check and when setting to null.
Sadly you still need to ! in quries
Exactly.
What we need is someone to create an analyzer that recognises when you are writing an ef query or if you’ve included and disabled the warnings.
The actual issue is using the same model for the database and query results. I.e. it’s not nullable in the database but could be after a query. But there’s no nice way to implement this without mapping everything to a dto.