Project
ReSharper
Priority
Critical
Type
Bug
Fix versions
4.5, 4.5.1, 5.0
State
Fixed
Assignee
Sergey Shkredov
Subsystem
Naming
Affected versions
No Affected versions
Fixed in build
5.0.1612.107  
  • Created by   Mel Grubb
    2 years ago (16 Apr 2009 17:33)
  • Updated by   Mel Grubb
    2 years ago (20 Apr 2009 15:14)
  • Jira: RSRP-103912
    (history, comments)
 
RSRP-103912 Need non-public version of "Static readonly fields" naming rule.
0
Issue is visible to: All Users
  The issue is visible to the selected user group only
There seems to be only one naming rule for all static read-only fields. Other field naming rules have public and non-public versions. I would suggest that this rule also needs public and non-public versions. For example, the following field declaration gets a naming suggestion to capitalize the "s" in the field name. Since this is a private field, I would think that the lower-case "s" would be appropriate in this case.

private static readonly int?[] supportedCollectionTypeIndicatorValues = new int?[] { 0, 1, 2, 3, 4, 5, 6 };


Issue was closed
Comments (0)
 
History
 
Linked Issues (?)
 
TeamCity Changes (0)
 
Issue has no comments