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
At the moment jsctags reports tags for imported content, e.g.:
import {foo, bar} from './myModule';
export default foo(bar());
will report the tags foo and bar. This leads to the problem that pressing ctrl+] on foo in line 3, vim will jump to line 1. What I really want is jumping to the definition of foo in './myModule' and not the local declaration of foo. Not reporting the import statements would lead to:
pro
easy jumping between files
smaller tag files
contra
no listing of declarations from import statements in Tagbar or something like that
In my opinion the pros have more weight than the cons, thoughts?
The text was updated successfully, but these errors were encountered:
Ok, upon further reading:
This is not an issue with jsctags. When you work with g] you can see that all relevant tags are there, ready to be used. It is more of a problem with vim and tag navigation. Heres something to read on that (and some some solutions which work quite well).
At the moment jsctags reports tags for imported content, e.g.:
will report the tags
foo
andbar
. This leads to the problem that pressingctrl+]
onfoo
in line 3, vim will jump to line 1. What I really want is jumping to the definition of foo in './myModule' and not the local declaration of foo. Not reporting theimport
statements would lead to:In my opinion the pros have more weight than the cons, thoughts?
The text was updated successfully, but these errors were encountered: