[#RSRP-29722] "Move Nested Type to Outer Scope": Wrong Editbox Label

ReSharper

"Move Nested Type to Outer Scope": Wrong Editbox Label

Created: 11 Oct 06 21:37 Updated: 20 Jun 07 10:57

Component/s:

Refactorings - Move Type to Outer Scope

Fix Version/s:

4.0

Security Level:

Everybody (All jira users)

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Description

« Hide

In the window there's an editbox to ask for a new name for the class being moved. Currently, it reads "Outer type name:". As I invoked the "Move to outer scope" action, I can mistake this for the name of the outer scope to put the class into. Eg, in the "

class A { class B { class C { } } }

" case and moving C to the outer scope, it's unclear whether it's the new name for C or the name of A.

Solution:

either rename the label to read "Rename the class:",
or avoid uniting "Move" and "Rename" refactorings and assume that user will invoke the Rename refactoring separately, if he really needs it.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Serge Baltic - 11 Oct 06 21:37

Rate pls.

[ Permlink | « Hide ]

Serge Baltic - 17 Jan 07 01:48

The issue probably goes to me?

[ Permlink | « Hide ]

Andrey Simanovsky - 18 Jan 07 14:22

If the first policy applies then yes.