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
Is your enhancement request related to a problem? Please describe.
When looking at an import, it's not obvious at a glance what package it comes from.
Describe the solution you'd like
There is a syntactically valid way to show what packages imports come from: PackageImports! So we can have inlay hints where inserting the inlay hints gives valid Haskell, which is quite nice.
Something like this:
import <hint>"base"</hint> Data.List
Describe alternatives you've considered
We already show packages and versions when hovering on imports, but this makes it even more immediate. It's probably going to be a bit of a love-it-or-hate it thing. And PackageImports is I think "discouraged" so maybe we shouldn't be encouraging people to use it.
The text was updated successfully, but these errors were encountered:
Is your enhancement request related to a problem? Please describe.
When looking at an import, it's not obvious at a glance what package it comes from.
Describe the solution you'd like
There is a syntactically valid way to show what packages imports come from:
PackageImports
! So we can have inlay hints where inserting the inlay hints gives valid Haskell, which is quite nice.Something like this:
Describe alternatives you've considered
We already show packages and versions when hovering on imports, but this makes it even more immediate. It's probably going to be a bit of a love-it-or-hate it thing. And
PackageImports
is I think "discouraged" so maybe we shouldn't be encouraging people to use it.The text was updated successfully, but these errors were encountered: