Project
ReSharper
Priority
Normal
Type
Feature
Fix versions
Mirabile Futurum
State
Open
Assignee
Kirill Skrygan
Subsystem
Go to by Name
Affected versions
No Affected versions
Fixed in build
No Fixed in build
  • Created by   Dmitry Shaporenkov
    4 years ago (09 Mar 2007 15:41)
  • Updated by   Ilya Ryzhenkov
    9 months ago (13 Apr 2011 03:55)
  • Jira: RSRP-36866
    (history, comments)
 
RSRP-36866 Go To Type: Emphasize nested types so that can be easily distinguishable from top-level types
0
Issue is visible to: All Users
  The issue is visible to the selected user group only
It is now impossible to visually determine if a type listed in Go To Type is a nested type or a top-level type
Comments (3)
 
History
  
Linked Issues (?)
 
TeamCity Changes (0)
 
Dmitry Shaporenkov
  Dmitry Shaporenkov
09 Mar 2007 15:44
4 years ago
I think it would be enough to change the visual style (e.g. font effect) of the 'in ...' phrase, so that the last components of the fully qualified name in this phrase (types) would have different visual style than the first components (namespaces)
Ilya Ryzhenkov
  Ilya Ryzhenkov
19 Mar 2007 17:25
4 years ago
May be show only namespaces to the right and display nested types as "OuterType.NestedType", and filter with "OR" for all types in nesting chain. I.e. "OuterType.NestedType" will be in list when "OT" or "NT" is typed.
Dmitry Shaporenkov
  Dmitry Shaporenkov
19 Mar 2007 17:39
4 years ago
I like the first part (display nested types with qualification and only namespaces to the right), but filtering with 'or' junction seems confusing to me. The behavior of the filtering shouldn't depend on that the type is a nested or a top-level (since the user may not know this) - only presentation should. In case if the are multiple levels of nesting, we could just show the first containing outer type, ellipsis and the name of the nested type (i.e. "OuterType1...NestedType)