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
Revert EF Core 8 navigation naming fix #2143
Comments
@hallidev @bclementfidx "UseLegacyNavigationNaming" for example |
I recommend "UseImprovedNavigationNaming" but "Legacy" works too :) |
I am considering "UsePrefixNavigationNaming" ... |
I implemented a fix for this in the latest daily build, would be grateful if you could try it out. (There is no UI for the feature, you must manually edit the efpt.config.json file) |
This worked for me, appreciate it! A lot of our devs use the cli.. so we're hoping the efcore team will revert this soon |
@bclementfidx This fix is also included the EF Core Power Tools CLI! |
@lupusbytes FYI |
dotnet/efcore#32981 (comment)
The text was updated successfully, but these errors were encountered: