Handle file rename in .cabal file#4961
Open
VeryMilkyJoe wants to merge 2 commits into
Open
Conversation
VeryMilkyJoe
force-pushed
the
rename-file-cabal
branch
from
f01a8c6 to
f939273
Compare
On WillRename Notification, edit the responsible .cabal file to change the module name entry of the renamed module to the new name.
VeryMilkyJoe
force-pushed
the
rename-file-cabal
branch
from
f939273 to
cfbbef1
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
On a
WillRenameFileNotification, we find the responsible.cabalfile for the old filepath and replace the corresponding module path with the module path for the new file name.This is part of the implementation of #4951.
Note that this is still missing some tests.
Screencast.From.2026-06-08.10-19-12.mp4