Project
ReSharper
Priority
Critical
Type
Feature
Fix versions
6.0 Beta
State
Fixed
Assignee
Kirill Skrygan
Subsystem
Go to by Name
Affected versions
No Affected versions
Fixed in build
6.0.2155.137  
  • Created by   Vladimir Reshetnikov
    5 years ago (20 Dec 2006 20:25)
  • Updated by   Andrew Serebryansky
    8 months ago (27 May 2011 22:45)
  • Jira: RSRP-33763
    (history, comments)
 
RSRP-33763 Ctrl+N dialog does not accept fully qualified name of a class
0
Issue is visible to: All Users
  The issue is visible to the selected user group only
Ctrl+N dialog does not accept fully qualified name of a class.
Maybe, it is by design?
But I need a cool window where I can pase FQN and navigate to the source.
Ctrl+N dialog looks like a suitable palce for it.

Use the following rule: if text in dialog contains period, treat it as FQN.
Comments (1)
 
History
 
Linked Issues (?)
 
TeamCity Changes (0)
 
Ilya Ryzhenkov
  Ilya Ryzhenkov
05 Feb 2007 16:53
5 years ago
Matching rules:

If pattern contains ".":
  • use FQN for the match, otherwise use Short Name.
  • dots separating namespaces may be ommited, i.e. SD. and S.D. match same set of namespaces.
  • namespace pattern should match any part of namespace, but not in the middle of the identifier

E.g:
  • SD.P matches System.Drawing.Point, but not JetBrains.ReSharper.TextControl.Graphics.Point
  • S.ISP matches System.IServiceProvider, System.Security.ISecurityPolicyEncodable, and System.Configuration.ISettingsProviderService
  • TC. should match "JetBrains.ReSharper.TextControl", "J.R.TextControl.Actions", etc. But not "J.R.AdvancedToolContainer". Using "*TC." should match "AdvancedToolContainer".

All in all, rules should be thought out better and experimental implementation should be done for dogfooding.