You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the features that gets a little of fear while working with newcomers is a toplevel open. The reasoning is to make sure that you are aware from which modules came your fns/values.
But I believe it could be a tooling issue, where we the editor can render the list of values used. I'm aware that you can hover on the module and the interface will be rendered.
I'm not sure what's the best interface for solving this, both lenses and dimming what isn't used seems like a valid approach but I don't want to propose a solution.
The text was updated successfully, but these errors were encountered:
ocamllsp has a code action "put module name in identifiers" (see https://github.com/ocaml/ocaml-lsp/blob/master/CHANGES.md#features-7) that allows to prepend the module name to all identifiers that come from that module. The code action can be run when the cursor is on an open statement. After the run, VCS should show all places that added this prefix. Hacky but I do it sometimes, and it's fine
A better solution we could implement:
I think we could use inlay hints (grayed out text within your editor) to render module names as prefixes to values that come from it. It shouldn't be difficult to do, but last time I tried, ocamllsp seemed to be sluggish to handle inlay hints requests
Hi,
One of the features that gets a little of fear while working with newcomers is a toplevel open. The reasoning is to make sure that you are aware from which modules came your fns/values.
But I believe it could be a tooling issue, where we the editor can render the list of values used. I'm aware that you can hover on the module and the interface will be rendered.
I'm not sure what's the best interface for solving this, both lenses and dimming what isn't used seems like a valid approach but I don't want to propose a solution.
The text was updated successfully, but these errors were encountered: