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
When developing we almost always deal with the same packages and there is absolutely no benefit in seeing the package path all the time. On the contrary, debugging becomes inefficient because some long packages makes you scroll horizontally to see what exactly is the type.
Example:
Would you great to be able to configure certain packages to be displayed as aliases. For example:
github.com/sourcenetwork/defradb -> defradb
github.com/golang-migrate/migrate -> migrate
github.com/testcontainers/testcontainers-go -> testcontainers
There is a variable "substitutePath" that does something similar, but it's for mapping local paths to remote ones.
The text was updated successfully, but these errors were encountered:
When developing we almost always deal with the same packages and there is absolutely no benefit in seeing the package path all the time. On the contrary, debugging becomes inefficient because some long packages makes you scroll horizontally to see what exactly is the type.
Example:
Would you great to be able to configure certain packages to be displayed as aliases. For example:
github.com/sourcenetwork/defradb -> defradb
github.com/golang-migrate/migrate -> migrate
github.com/testcontainers/testcontainers-go -> testcontainers
There is a variable "substitutePath" that does something similar, but it's for mapping local paths to remote ones.
The text was updated successfully, but these errors were encountered: