Add support for the "Move to file" interactive code action #987
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Aug 31, 2025
rchl
reviewed
Sep 12, 2025
rchl
reviewed
Sep 12, 2025
1 task
…on + check kind instead of name
rchl
reviewed
Sep 13, 2025
rchl
reviewed
Sep 13, 2025
Contributor
Author
|
I noticed that the client actually only receives the kind |
rchl
approved these changes
Sep 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support for the "Move to file" code action, fixing #863.
This pull request does the following:
supportsMoveToFileCodeActioninitialization option so that the change is opt-inmoveToFileCodeActionSupportflag infeaturesincludeInteractiveCodeActionsflag totrueingetRefactors, provided that the client does support the "Move to file" code actionprovideRefactors(as there could be other interactive code actions that would require separate opt-in)notApplicableReason(this is specific to interactive code actions as for instance "Move to file" may fail if you provide an invalid file name, which is only known when applying the code action).See also emacs-lsp/lsp-mode#4866 for an implementation of it in Emacs'
lsp-mode.