Skip to content

Direct component resolution in VS Code #732

@wmelton

Description

@wmelton

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy