Not all databases are created with the same semantics. The rules for generating Navigation Names in EFcore appear to be hard coded in method StripId(), and those rules are (1) the field must end in "id" and (2) it may end in "guid" to be a candidate navigation name.

Our UUID/GUID Primary Key fields end in "_uid" which causes the navigation items to end up with a U at the end, such as RoleU. We also store human readable, string based primary keys in fields that end in "_code" so these navigation items would end up as similar to "PersonnelTypeCodeNavigation".

I request adding a (command line) configuration item to be passed in to scaffold generation such that custom suffixes can be defined. In our case this would include "uid" and "code". I would also. request that StripId be refactored or renamed such not all suffixes have to end in "id".