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

Direct component resolution in VS Code #732

Open
3 tasks done
wmelton opened this issue Jan 25, 2024 · 0 comments
Open
3 tasks done

Direct component resolution in VS Code #732

wmelton opened this issue Jan 25, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@wmelton
Copy link

wmelton commented Jan 25, 2024

Clear and concise description of the problem

This may be a limitation of VS Code, but in VS Code if you option click a component name within Nuxt, rather than drilling directly to the component file, it takes you to components.d.ts where you then must drill on the resolved path for the component.

Suggested solution

If VS Code will allow it, it would be excellent if there was a way to drill directly to the component rather than the intermediate components.d.ts file. This would keep the workspace cleaner as well since components.d.ts gets needlessly opened in the tabs and left open once you arrive at the final file you actually need to edit.

Alternative

No response

Additional context

No response

Validations

@wmelton wmelton added the enhancement New feature or request label Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant