HasKey Reference Left Out with Non-Conventional Key Property

[davidhendrickmb]

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

[ErikEJ]

Or maybe the Key attribute?

[tonysneed]

Thanks for reporting the bug. I'll work on fixing it.

[davidhendrickmb]

Thank you :)
If you happen to find a temporary workaround please let me know as I'm trying to test out Net 6 upgrade.

[tonysneed]

@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: AccompanimentTypeId

[ErikEJ]

Potential duplicate: ErikEJ/EFCorePowerTools#1256

[RaulFunezp]

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.
Thank you

[tonysneed]

@ErikEJ @davidhendrickmb @RaulFunezp Fixed with Handlebars v6.0.3.

[davidhendrickmb]

Thanks Tony, much appreciated!