This project is read-only.

Creation of a new rule(s)

Jul 16, 2012 at 11:07 AM


Could you look into introducing a new rule to allow the groupping of enums into an enums.cs files?

The reasoning is that i'm currently working with a lot of serialization classes and it would be nice if i could keep these together in a file. If this is acceptable could we also look at a similar thing for consts?




Jul 16, 2012 at 6:23 PM

While I wouldn't be opposed to allowing the condition, I'll tell you why our team prefers to keep enums one-per-file. It's for file-based version control purposes: it's easier to get a scope of what changed if the granularity is at the file (and therefore enum) level. If you put all of your enums in one file, that file is going to have a lot more change activity, which makes it slightly harder to see what changed at a glance.