Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 Investigate use of Nullable Strongly Typed IDs #329

Open
danielmackay opened this issue May 30, 2024 · 0 comments
Open

🐛 Investigate use of Nullable Strongly Typed IDs #329

danielmackay opened this issue May 30, 2024 · 0 comments
Labels
Type: Bug A problem with existing functionality

Comments

@danielmackay
Copy link
Member

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/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug A problem with existing functionality
Projects
Development

No branches or pull requests

1 participant