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
HasKey Reference Left Out with Non-Conventional Key Property #203
Comments
Or maybe the Key attribute? |
Thanks for reporting the bug. I'll work on fixing it. |
Thank you :) |
@davidhendrickmb I am looking at this now. It has to do with the PK not following EF Core naming conventions. I will fix the bug, but if you wish to have a workaround, simply make sure your PK entity property follows the standard EF Core naming convention for key fields. In other words, entitynameId. In your case this would be: |
Potential duplicate: ErikEJ/EFCorePowerTools#1256 |
I have exactly the same problem when using HandleBars in ErikEJ/EfCorePowerTools. The name of my HasKey not generated is like this: AeDeCtaCB. I hope that when Tony solves that bug, it will solve my case too. |
@ErikEJ @davidhendrickmb @RaulFunezp Fixed with Handlebars v6.0.3. |
Thanks Tony, much appreciated! |
Hi there,
This is in relation to the issue here which Erik has mentioned is a problem with this package.
The HasKey reference is being left out when I use Handlebars templates with EF Core 6. Would you know of a fix for this?ErikEJ/EFCorePowerTools#1250
Thanks,
David
The text was updated successfully, but these errors were encountered: