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
- Extract
A014.zip.
- Open the extracted
A014 directory directly in VS Code.
- Wait until the Vizsla workspace scan is complete.
- Open
src/a014_top.sv.
- Run Go to Definition on
a014_pkg_t in a014_pkg_t pkg_value;.
- 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.
typedef usage from package import cannot navigate to definition
A014.zip
Environment
v0.1.1vizsla 0.1.0_RELEASE+6d9befd.20260519T100848ZAttachment
Please use the attached
A014.zip. Extract it, then open the extractedA014directory directly in VS Code as the workspace root.Source files:
vizsla_config.tomlsrc/a014_top.svsrc/a014_pkg.svReproduction Steps
A014.zip.A014directory directly in VS Code.src/a014_top.sv.a014_pkg_tina014_pkg_t pkg_value;.src/a014_pkg.sv.Actual Behavior
src/a014_top.svhas no diagnostics.a014_pkg_thas no unknown type diagnostic.Expected Behavior
import a014_pkg::*;, thea014_pkg_tusage should navigate to its typedef definition insrc/a014_pkg.sv.