Project
ReSharper
Priority
Normal
Type
Cosmetics
Fix versions
6.0 EAP
State
Fixed
Assignee
Slava Tutushkin
Subsystem
Typing Assistance
Affected versions
No Affected versions
Fixed in build
No Fixed in build
  • Created by   Ilya Ryzhenkov
    5 years ago (05 Aug 2006 02:12)
  • Updated by   Sergey Shkredov
    4 weeks ago (26 Apr 2012 17:49)
  • Jira: RSRP-5735
    (history, comments)
 
RSRP-5735 Move members cosmetics
0
Issue is visible to: All Users
  The issue is visible to the selected user group only
There are few cosmetic issues with moving members. First, fields are not movable when caret is on the modifiers or type. It only initiated on field identifier or initalization expression.
Second, when there are regions, they are not taken into consideration and thus some oddity reveals. You can't move member inside empty region, so if you move last member from region, you can't move it back. Also ordering is quite weird when regions are involved. I would suggest including begin and end region tags in the list of targets for swap. This would make it much cleaner in this case.
Comments (2)
 
History
 
Linked Issues (?)
 
TeamCity Changes (0)
 
Jura Gorohovsky
  Jura Gorohovsky
09 Dec 2010 01:55
17 months ago
Everything is reproducible in ReSharper 5. In addition, moving code with the caret on a modifier moves the containing block instead (class)
Slava Tutushkin
  Slava Tutushkin
27 Jan 2011 23:02
15 months ago
All of this is fixed in R6
Related Changes
Resolved Date
15 months ago (27 Jan 2011 23:02)
State
OpenFixed