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.

Sign up for GitHub

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

Jump to bottom

Add support for handling moved files #191

Closed
Pajn opened this issue Feb 26, 2017 · 4 comments
Closed

Add support for handling moved files #191

Pajn opened this issue Feb 26, 2017 · 4 comments
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality

Comments

@Pajn
Copy link

Pajn commented Feb 26, 2017

When a file is moved or renamed many languages would need to update import paths and maybe even symbol names.
I can't see a good way to handle that with the current API, would it be possible to add a request for that?
@dbaeumer dbaeumer added this to the Backlog milestone Mar 7, 2017
@dbaeumer
Copy link
Member

dbaeumer commented Mar 7, 2017

Yes, it makes sense to provide a move refactoring request.

@dbaeumer dbaeumer added the feature-request Request for new features or functionality label Apr 12, 2017
@rcjsuen rcjsuen mentioned this issue Jul 21, 2017
Closed
@tsmaeder tsmaeder mentioned this issue Sep 25, 2017
Closed
@fbricon
Copy link
Contributor

fbricon commented Oct 10, 2017 •
edited

We're gonna need that feature for Java support (eclipse-jdtls/eclipse.jdt.ls#363). Any way to prioritize this? cc @aeschli @akaroml @tsmaeder

@tsmaeder tsmaeder mentioned this issue Oct 16, 2017
Closed
@dbaeumer
Copy link
Member

The best way to speed this up is to provide a PR. But this needs to happen in the protocol, the node libraries and very likely in VS Code as well.

@dbaeumer
Copy link
Member

Closing in favor of #272

@dbaeumer dbaeumer added the *duplicate Issue identified as a duplicate of another issue(s) label Nov 17, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 1, 2018
@dbaeumer dbaeumer removed this from the Backlog milestone Nov 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fbricon @Pajn @dbaeumer