Project
ReSharper
Priority
Normal
Type
Bug
Fix versions
Mirabile Futurum
State
Open
Assignee
Sergey Shkredov
Subsystem
Naming
Affected versions
No Affected versions
Fixed in build
No Fixed in build
  • Created by   Greg Law
    4 years ago (24 Jun 2007 01:59)
  • Updated by   Greg Law
    2 years ago (08 Apr 2009 20:43)
  • Jira: RSRP-44079
    (history, comments)
 
RSRP-44079 Encapsulate field in nested class
0
Issue is visible to: All Users
  The issue is visible to the selected user group only
When encapsulating a field in a nested class or structure that contains the same name as a property in the parent class, ReSharper complains that the name conflicts. As an example, given this class:

public class A
{
private int _field;

public int Field
{
get { return _field; }
set { _field = value; }
}

private struct B
{
internal int _field;
}
}

Attempting to encapsulate B._field with a property named Field results in the message "Conflict on property A.Field" even though the names do not conflict.
Comments (0)
 
History
 
Linked Issues (?)
 
TeamCity Changes (0)
 
Issue has no comments