Entity level attributes should use nameof() to facilitate refactoring

[InsanePup]

Not a bug per se, but a definite improvement to usability. When specifying property names, nameof() should be used to facilitate refactoring. Example of where this should be done...

[Table("ec_code")]
**[Index("CodeId", Name = "code_id", IsUnique = true)]**
[MySqlCharSet("utf8mb3")]
[MySqlCollation("utf8mb3_general_ci")]
public partial class EcCode
{

[ErikEJ]

I think this is by design, as nameof us not always correct.

[InsanePup]

I think this is by design, as nameof us not always correct.

Why not use it when it is correct?

[ErikEJ]

See this issue for more context: dotnet/efcore#26588

[InsanePup]

I don't want to beat this to death, so please don't feel obliged to reply... but...
There are obviously scenarios where nameof() is appropriate, for instance in my original post. The Index attribute references a property in the same class. If you're saying that you can't reliably distinguish these scenarios then fair enough. For context, I encountered this issue within 30 minutes of first using the Power Tools, so it wasn't some rare edge case, at least for me. The capitalization of generated entity and property names is not perfect so I had quite a bit of clean-up to do, and refactoring tools are often less than perfect too.

On a tangent... Thank you for providing this tool. It has been a great time saver. If I was to suggest a feature for a future version, it would be the ability to specify relationship between entities prior to code generation. The MySQL db I am currently using does not have foreign keys explicitly defined, so I need to add code for the all the navigation properties, which has been a simple but cumbersome task.