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
I'm using Nuxt, and Nuxt maps the "root" directory to ~~. Because of this mapping, VSCode will often autocomplete paths to, say, a script file, to something like:
import{Foo}from'~~/legacy/scripts/Foo'
However, to reduce verbosity in commonly-used paths, I have aliases like ~js to refer to ~~/legacy/scripts.
What I would like is the ability to rewrite not just relative paths to alias paths, but alias paths to other alias paths.
So, on save (or eslint --fix), I would like the above re-written to:
import{Foo}from'~js/Foo'
Is it possible to include more customization into what is re-written? This seems somewhat related to #133, in that some customization / filters would be nice.
The text was updated successfully, but these errors were encountered:
Any proposal on how to solve this? I had the case that I have multiple aliases and one of then is a subpath of another one and the plugin should always select the inner most one but not sure if that totally solves the issue.
I'm using Nuxt, and Nuxt maps the "root" directory to
~~
. Because of this mapping, VSCode will often autocomplete paths to, say, a script file, to something like:However, to reduce verbosity in commonly-used paths, I have aliases like
~js
to refer to~~/legacy/scripts
.What I would like is the ability to rewrite not just relative paths to alias paths, but alias paths to other alias paths.
So, on save (or eslint --fix), I would like the above re-written to:
Is it possible to include more customization into what is re-written? This seems somewhat related to #133, in that some customization / filters would be nice.
The text was updated successfully, but these errors were encountered: