[#1748] Fix mangled module names on hovering
Motivation and Context
Problem
If we hover over the imported module then we'll see something
like Mangled_module__bla__bla__Module____mligo
. It's kinda confusing.
We need to show there something more proper.
Solution
Run a dependency_graph
function on a given file, extract
(filename * module_name) list
from its result, pass it into scopes
and substitute the file name instead of the mangled name if needed.
Related issues
Resolves #1748 (closed) .
✅ Checklist for the LIGO Language Server
- I checked whether I need to update the
README.md
file for the plugin and did so if necessary:-
If I implemented a new LSP request, I added it to the list of supported features that may be disabled -
If I implemented a new LSP method, I added it to the list of supported functionality
-
-
I checked that my changes work in Emacs, Vim, and Visual Studio Code -
(Before merging) The commit history is squashed and prettified, and follows the Serokell commit policy, or the MR is set to squash the commits
Description
Component
-
compiler -
website -
webide -
vscode-plugin -
debugger
Types of changes
-
Bug fix (non-breaking change which fixes an issue) -
New feature (non-breaking change which adds functionality) -
Breaking change (fix or feature that would cause existing functionality to not work as expected) -
Performance improvement (non-breaking change that improves performance) -
None (change with no changelog)
Changelog
Fixed mangled module names on imports hovering. Now you can see the correct file paths like:
module K = "../A.mligo"
Checklist:
-
Changes follow the existing coding style (use dune @fmt
to check). -
Tests for the changes have been added (for bug fixes / feature). -
Documentation has been updated. -
Changelog description has been added (if appropriate). -
Start titles under ## Changelog
section with #### (if appropriate). -
There is no image or uploaded file in changelog -
Examples in changed behaviour have been added to the changelog (for breaking change / feature).