Erronious "hidden" icon?
I have a class that, somewhere up the hierarchy tree, derives from a public
interface that has a property defined called "Name".
When I attempt to add a Name property to this class, it shows the black "X"
hidden icon in the left column.
But the fact is, that Name property isn't rally hidden at all. Everything
compiles fine. C# is totally okay with this. The interface is defined
fully qualified, and if you want to use that property, you'd cast it to be
the interface anyway, so there just isn't a conflict here, yet ReSharper
keeps putting that X there. I like to run with 'clean' files in my projects
(all green, no black "X").
Is this by design, or is this a bug? I'm more curious than anything at this
point, but I wish there were some way for me to have ReSharper not put that
icon there when it really wasn't hurting anything.
Please sign in to leave a comment.
Is your example like this:
interface I
{
public int Prop{ get; }
}
class B : I
{
public int Prop{ get{ return 1; }
}
class A : B
{
public int Prop{ get{ return 2; }
}
?
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Almost but not quite ... in the declaration of class B:I, it says:
class B : I
{
public int I.Prop { get { return 1; }
}
The name is fully qualified with the interface name.
Thus there shouldn't be any conflict or hiding going on.
"Valentin Kipiatkov (JetBrains)" <valentin@jetbrains.com> wrote in message
news:427727632455390480963922@news.intellij.net...
>
>
>
>
>
>
>
>> I have a class that, somewhere up the hierarchy tree, derives from a
>> public interface that has a property defined called "Name".
>>
>> When I attempt to add a Name property to this class, it shows the
>> black "X" hidden icon in the left column.
>>
>> But the fact is, that Name property isn't rally hidden at all.
>> Everything compiles fine. C# is totally okay with this. The
>> interface is defined fully qualified, and if you want to use that
>> property, you'd cast it to be the interface anyway, so there just
>> isn't a conflict here, yet ReSharper keeps putting that X there. I
>> like to run with 'clean' files in my projects (all green, no black
>> "X").
>>
>> Is this by design, or is this a bug? I'm more curious than anything
>> at this point, but I wish there were some way for me to have ReSharper
>> not put that icon there when it really wasn't hurting anything.
>>
>
>
Hello Paul,
yes, this is indeed a bug. I've submitted a request for it to our tracker:
http://www.intellij.net/tracker/resharper/viewSCR?publicId=5951
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> Is your example like this:
>>
>> interface I
>> {
>> public int Prop{ get; }
>> }
>> class B : I
>> {
>> public int Prop{ get{ return 1; }
>> }
>> class A : B
>> {
>> public int Prop{ get{ return 2; }
>> }
>> ?
>>
>> Valentin Kipiatkov
>> Chief Scientist, Vice President of Product Development
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> I have a class that, somewhere up the hierarchy tree, derives from a
>>> public interface that has a property defined called "Name".
>>>
>>> When I attempt to add a Name property to this class, it shows the
>>> black "X" hidden icon in the left column.
>>>
>>> But the fact is, that Name property isn't rally hidden at all.
>>> Everything compiles fine. C# is totally okay with this. The
>>> interface is defined fully qualified, and if you want to use that
>>> property, you'd cast it to be the interface anyway, so there just
>>> isn't a conflict here, yet ReSharper keeps putting that X there. I
>>> like to run with 'clean' files in my projects (all green, no black
>>> "X").
>>>
>>> Is this by design, or is this a bug? I'm more curious than anything
>>> at this point, but I wish there were some way for me to have
>>> ReSharper not put that icon there when it really wasn't hurting
>>> anything.
>>>
Dmitry,
I see this bug, 5951, is fixed in build 200. This means it won't be getting
fixed in a point release of 1.5? I was hoping this fix would make it into
1.5.1 or at least 1.5.x ...
Just curious.
- Paul
"Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
news:14432632455658588245015@news.intellij.net...
>
>
>
>> Almost but not quite ... in the declaration of class B:I, it says:
>>
>> class B : I
>> {
>> public int I.Prop { get { return 1; }
>> }
>> The name is fully qualified with the interface name.
>>
>> Thus there shouldn't be any conflict or hiding going on.
>>
>> "Valentin Kipiatkov (JetBrains)" <valentin@jetbrains.com> wrote in
>> message news:427727632455390480963922@news.intellij.net...
>>
>>> Is your example like this:
>>>
>>> interface I
>>> {
>>> public int Prop{ get; }
>>> }
>>> class B : I
>>> {
>>> public int Prop{ get{ return 1; }
>>> }
>>> class A : B
>>> {
>>> public int Prop{ get{ return 2; }
>>> }
>>> ?
>>>
>>> Valentin Kipiatkov
>>> Chief Scientist, Vice President of Product Development
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
>>>> I have a class that, somewhere up the hierarchy tree, derives from a
>>>> public interface that has a property defined called "Name".
>>>>
>>>> When I attempt to add a Name property to this class, it shows the
>>>> black "X" hidden icon in the left column.
>>>>
>>>> But the fact is, that Name property isn't rally hidden at all.
>>>> Everything compiles fine. C# is totally okay with this. The
>>>> interface is defined fully qualified, and if you want to use that
>>>> property, you'd cast it to be the interface anyway, so there just
>>>> isn't a conflict here, yet ReSharper keeps putting that X there. I
>>>> like to run with 'clean' files in my projects (all green, no black
>>>> "X").
>>>>
>>>> Is this by design, or is this a bug? I'm more curious than anything
>>>> at this point, but I wish there were some way for me to have
>>>> ReSharper not put that icon there when it really wasn't hurting
>>>> anything.
>>>>
>
>
Hello Paul,
build 200 means ReSharper 2.0 that we plan to open for EAP soon. We'll consider
including the fix into 1.5.x but I'm not sure if this is safe enough to do
now.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> Hello Paul,
>>
>> yes, this is indeed a bug. I've submitted a request for it to our
>> tracker:
>> http://www.intellij.net/tracker/resharper/viewSCR?publicId=5951
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Almost but not quite ... in the declaration of class B:I, it says:
>>>
>>> class B : I
>>> {
>>> public int I.Prop { get { return 1; }
>>> }
>>> The name is fully qualified with the interface name.
>>> Thus there shouldn't be any conflict or hiding going on.
>>>
>>> "Valentin Kipiatkov (JetBrains)" <valentin@jetbrains.com> wrote in
>>> message news:427727632455390480963922@news.intellij.net...
>>>
>>>> Is your example like this:
>>>>
>>>> interface I
>>>> {
>>>> public int Prop{ get; }
>>>> }
>>>> class B : I
>>>> {
>>>> public int Prop{ get{ return 1; }
>>>> }
>>>> class A : B
>>>> {
>>>> public int Prop{ get{ return 2; }
>>>> }
>>>> ?
>>>> Valentin Kipiatkov
>>>> Chief Scientist, Vice President of Product Development
>>>> JetBrains, Inc
>>>> http://www.jetbrains.com
>>>> "Develop with pleasure!"
>>>>> I have a class that, somewhere up the hierarchy tree, derives from
>>>>> a public interface that has a property defined called "Name".
>>>>>
>>>>> When I attempt to add a Name property to this class, it shows the
>>>>> black "X" hidden icon in the left column.
>>>>>
>>>>> But the fact is, that Name property isn't rally hidden at all.
>>>>> Everything compiles fine. C# is totally okay with this. The
>>>>> interface is defined fully qualified, and if you want to use that
>>>>> property, you'd cast it to be the interface anyway, so there just
>>>>> isn't a conflict here, yet ReSharper keeps putting that X there.
>>>>> I like to run with 'clean' files in my projects (all green, no
>>>>> black "X").
>>>>>
>>>>> Is this by design, or is this a bug? I'm more curious than
>>>>> anything at this point, but I wish there were some way for me to
>>>>> have ReSharper not put that icon there when it really wasn't
>>>>> hurting anything.
>>>>>