LSP `WillRenameFiles` implementation doesn't adjust relative imports

[smheidrich]

Describe the Bug

Pyrefly's LSP server implementation only adjusts absolute imports when it gets a renamed-file notification (WillRenameFiles / DidRenameFiles¹) from the client, but not relative ones.

To reproduce:

1. Create a Python package pkg/__init__.py with modules pkg/a.py and pkg/b.py.
2. Define a function in a.py:

   def foo(): ...

3. Import this function from b.py:

   from .a import foo
   foo()

4. In your editor with Pyrefly attached as an LSP server, rename a.py to a2.py and notice that the import in b.py remains unchanged.

Whereas if you instead have from pkg.a import foo in b.py, the import is updated to say pkg.a2 as it should.

^{1 Although I think Pyrefly only implements the former}

Sandbox Link

No response

(Only applicable for extension issues) IDE Information

No response

Note: I tested this in Neovim with neo-tree and nvim-lsp-file-operations, but as it worked fine for absolute imports, it wouldn't make sense for the editor setup to be at fault.

[xaskii]

#claim

[github-actions]

@xaskii you've claimed this issue — it's now assigned to you. Thanks for picking it up! 🎉

[github-actions]

This issue has someone assigned, but has not had recent activity for more than 2 weeks.

If you are still working on this issue, please add a comment so everyone knows. Otherwise, please unassign yourself and allow someone else to take over.

Thank you for your contributions!

[xaskii]

submitting a PR in a sec, sry bot