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

BUG in Refactor: move to new file #242499

Open
psnet opened this issue Mar 3, 2025 · 1 comment
Open

BUG in Refactor: move to new file #242499

psnet opened this issue Mar 3, 2025 · 1 comment
Assignees

Comments

@psnet
Copy link

psnet commented Mar 3, 2025

Does this issue occur when all extensions are disabled?: Yes

Version: 1.97.2 (user setup)
Commit: e54c774

Steps to Reproduce:

  1. For example
/**
 * Description
 */
export const NAME1 = 3;
  1. Use Refactor: move to new file for this variable
  2. New filename is not asked during this step
@justschen
Copy link
Contributor

cc. @mjbvz wasn't move to new file meant to be deprecated at some point?

@psnet a workaround for the time being is just using the Move to File, which should prompt the quickpick to open.

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

No branches or pull requests

3 participants