Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ctrl+left Buttom (Go to Definition) #2521

Closed
zengchulin opened this issue Dec 5, 2020 · 10 comments
Closed

Ctrl+left Buttom (Go to Definition) #2521

zengchulin opened this issue Dec 5, 2020 · 10 comments

Comments

@zengchulin
Copy link

zengchulin commented Dec 5, 2020

image

It is recommended to add Ctrl + left click on the component label and path to jump to the definition

@yoyo930021
Copy link
Member

Please provide a repro case.
Please read https://github.com/vuejs/vetur/blob/master/.github/NO_REPRO_CASE.md

@zengchulin
Copy link
Author

The component label for the VUE file cannot jump to the definition through F12

@zengchulin
Copy link
Author

Integration of vue-peek is recommended

@zengchulin zengchulin reopened this Dec 5, 2020
@zengchulin
Copy link
Author

Go to definition" doesn't work in .vue files

@yoyo930021
Copy link
Member

Vetur support it.
Please provide a repro case.
Otherwise we can do nothing.

@zengchulin
Copy link
Author

The recommended jump to the definition ignores index.vue or.vue that does not write the incoming path

@yoyo930021
Copy link
Member

Oh, please use .vue file extensions.
#423 (comment)

@zengchulin
Copy link
Author

WebStorm omits the file extensions by default (new project with Vue CLI). I can't find an IDE option to enforce extensions for .vue files and omit it for .js files. There is option to require to always add an extension
So to have code completion for all developers in my project I have to add .js extensions everywhere? Is that Vetur way of solving the problem for projects that use different editors?
I've tried to switch from WebStorm to VSCode (4 times by now) and these are the kind of issues that always bring me back to WebStorm.

@yoyo930021
Copy link
Member

WebStorm omits the file extensions by default (new project with Vue CLI). I can't find an IDE option to enforce extensions for .vue files and omit it for .js files. There is option to require to always add an extension
So to have code completion for all developers in my project I have to add .js extensions everywhere? Is that Vetur way of solving the problem for projects that use different editors?
I've tried to switch from WebStorm to VSCode (4 times by now) and these are the kind of issues that always bring me back to WebStorm.

vitejs/vite#178 (comment)
vuejs/vue-cli#6064
vuejs/vue-cli#5307

Vue CLI will drop this support in v5.

@yoyo930021
Copy link
Member

WebStorm omits the file extensions by default (new project with Vue CLI). I can't find an IDE option to enforce extensions for .vue files and omit it for .js files. There is option to require to always add an extension
So to have code completion for all developers in my project I have to add .js extensions everywhere? Is that Vetur way of solving the problem for projects that use different editors?
I've tried to switch from WebStorm to VSCode (4 times by now) and these are the kind of issues that always bring me back to WebStorm.

You can open issues what missing feature or bug back to WebStorm.
Take time to process slowly, Development time is limited. We can only improve slowly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants