Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Let users select the file name with running the 'Move to file' refactoring

See original GitHub issue

microsoft/vscode#50486

Currently if the new file cannot be resolved, it would be newFile.ts. Later I would have to manually update the filename. And in the case when updateImportsOnFileMove.enabled is set to falsey, I’ll have to rename the references to the new files too. Would be better to show an input for filename when no reasonable guess for the new file name exists.

Issue Analytics

State:
Created 5 years ago
Reactions:35
Comments:12 (1 by maintainers)

Top GitHub Comments

20reactions

hcharleycommented, Aug 4, 2021

Since it’s been a while, I’d like to express my interest in having this feature. It would be a big help to me to kebab case new file names automatically.

8reactions

sevenryzecommented, Sep 30, 2018

I suggest one more request, that for quick refactoring and consistency, we could use a flag like - nameStrategy: [common name strategy] - to quick move function to a new file.

Also, i think for now, the new files are always located in the current folder aside as original file, could we set a different file path when using the filename open box?