SA1649 conflicts with default Razor Pages file/class naming

When creating a Razor Page it will generate a .cshtml and .cshtml.cs files. The model used inside this file is postfixed with Model, which causes SA1649 to be violated.

Eg: When creating a Razor Page called Index, the files generated will be called Index.cshtml and Index.cshtml.cs, but the class generated will be called IndexModel.

Not sure if this case should be allowed in SA1649, as I don’t want to switch this rule off for the whole project and adding #pragma warning disable/restore to every Razor Page seems excessive to me?

[sharwell]

@daviddunson That should be possible using .editorconfig in 16.3.

[*.cshtml.cs]
dotnet_diagnostic.SA1649.severity = none

[af4jm]

@sharwell

I know I’m late to the party here, but your suggestion #2 would break the convention that’s been in place since the beginning of MVC where model classes end with the Model suffix to distinguish from similarly named objects (usually entities), #3 requires also renaming the .cshtml file, which is part of the URL.

The gotcha here is that in traditional MVC, the cshtml files had no code-behind & the models live in a separate folder… now with Razor Pages the model is the code-behind, which for many scenarios is much cleaner by having related pieces together, but does break this rule as the two long-standing conventions now conflict with each other.

It would be nice if rulesets could apply by subfolder instead of strictly at the project level, but I have a hunch the amount of effort required to make that happen means I’m not likely to see it anytime soon.

Meantime, as ugly as it is, I’m setting my convention to be the first line of all Razor Page code behinds/models is #pragma warning disable SA1649.