Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Move static members" prepends the current namespace twice after the textbox is edited #70895

Closed
xparadoxical opened this issue Nov 19, 2023 · 2 comments · Fixed by #76314
Closed

Comments

@xparadoxical
Copy link

xparadoxical commented Nov 19, 2023

Version Used:
VisualStudio.17.Release/17.8.0+34309.116
C# Tools 4.8.0-7.23558.1+e091728607ca0fc9efca55ccfb3e59259c6b5a0a
Steps to Reproduce:

  1. Use "Move static members to another type"
  2. Edit the Type Name textbox

Expected Behavior:
The type name doesn't contain the namespace twice.

Actual Behavior:
"New Type Name" has the namespace prepended twice.

The actual target seems to not contain the duplicated namespace and so this doesn't affect what the fixer does, e.g. NS.NS.T is displayed but NS.T is correctly selected (and created if needed).

2023-11-19.17-53-10.mp4
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Issues and PRs which have not yet been triaged by a lead label Nov 19, 2023
@jcouv jcouv added the Area-IDE label Dec 7, 2023
@arunchndr arunchndr added Feature - Move Static Members and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 27, 2024
@arunchndr arunchndr added this to the Backlog milestone Nov 27, 2024
@arunchndr arunchndr added the Bug label Nov 27, 2024
@arunchndr
Copy link
Member

This may have been fixed recently. Shen to validate and close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants