You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you add or remove migrations, a lot of garbage is generated in the code, making it difficult to analyze the changes in git.
Your code
Any code generates this behavior. The important thing is to call add-migration or remove-migration. It is always adding or removing this (string)null. for literally all tables. And this generates a lot of garbage in the code and when we are going to analyze the changes in the class before committing, it becomes very difficult because of this.
There has to be a standard for both actions. Either always put this or never put this.
EF Core version
9
Database provider
No response
Target framework
No response
Operating system
No response
IDE
No response
The text was updated successfully, but these errors were encountered:
Bug description
When you add or remove migrations, a lot of garbage is generated in the code, making it difficult to analyze the changes in git.
Your code
Any code generates this behavior. The important thing is to call add-migration or remove-migration. It is always adding or removing this (string)null. for literally all tables. And this generates a lot of garbage in the code and when we are going to analyze the changes in the class before committing, it becomes very difficult because of this.
There has to be a standard for both actions. Either always put this or never put this.
EF Core version
9
Database provider
No response
Target framework
No response
Operating system
No response
IDE
No response
The text was updated successfully, but these errors were encountered: