Skip to content

typedef usage from package import cannot navigate to definition #55

@linmoIO

Description

@linmoIO

typedef usage from package import cannot navigate to definition

A014.zip

Environment

  • OS: Windows
  • Vizsla release: v0.1.1
  • Server build: vizsla 0.1.0_RELEASE+6d9befd.20260519T100848Z

Attachment

Please use the attached A014.zip. Extract it, then open the extracted A014 directory directly in VS Code as the workspace root.

Source files:

  • vizsla_config.toml
  • src/a014_top.sv
  • src/a014_pkg.sv

Reproduction Steps

  1. Extract A014.zip.
  2. Open the extracted A014 directory directly in VS Code.
  3. Wait until the Vizsla workspace scan is complete.
  4. Open src/a014_top.sv.
  5. Run Go to Definition on a014_pkg_t in a014_pkg_t pkg_value;.
  6. Check whether it navigates to the typedef definition in src/a014_pkg.sv.

Actual Behavior

  • src/a014_top.sv has no diagnostics.
  • a014_pkg_t has no unknown type diagnostic.
  • Go to Definition returns an empty result and does not navigate to the typedef definition.

Expected Behavior

  • After import a014_pkg::*;, the a014_pkg_t usage should navigate to its typedef definition in src/a014_pkg.sv.

Metadata

Metadata

Assignees

No one assigned

    Labels

    known-limitThis is a known limit and may be implemented in future.packagesv-supportThis issue is related to system verilog supports.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions