Skip to content

Modules from libraries are semantically resolved but cannot navigate to definition #54

@linmoIO

Description

@linmoIO

Modules from libraries are semantically resolved but cannot navigate to definition

A011.zip

Environment

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

Attachment

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

Source files:

  • vizsla_config.toml
  • src/a011_top.sv
  • include/a011_defs.svh
  • lib/A011_LIB/vizsla_config.toml
  • lib/A011_LIB/src/a011_lib_child.sv

Reproduction Steps

  1. Extract A011.zip.
  2. Open the extracted A011 directory directly in VS Code.
  3. Wait until the Vizsla workspace scan is complete.
  4. Open src/a011_top.sv.
  5. Run Go to Definition on a011_lib_child in the instance, or Ctrl-click a011_lib_child.
  6. Check whether it navigates to module a011_lib_child in lib/A011_LIB/src/a011_lib_child.sv.

Actual Behavior

  • a011_lib_child has no unknown module diagnostic.
  • Workspace diagnostics include lib/A011_LIB/src/a011_lib_child.sv, so the library file is loaded.
  • Go to Definition / Declaration returns an empty result and does not navigate to the library module definition.

Expected Behavior

  • Since libraries = ["lib/A011_LIB"] is loaded and participates in semantic analysis, a011_lib_child in a011_top.sv should navigate to the module definition in lib/A011_LIB/src/a011_lib_child.sv.

Metadata

Metadata

Assignees

No one assigned

    Labels

    known-limitThis is a known limit and may be implemented in future.project model

    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