Skip to content

Rename misses package import usage even when scope visibility is public #79

@linmoIO

Description

@linmoIO

Rename misses package import usage even when scope visibility is public

A019.zip

Environment

  • OS: Windows
  • Vizsla release: v0.1.2
  • Server build: vizsla 0.1.0_RELEASE+43c5ed5.20260521T023910Z

Attachment

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

Source files:

  • vizsla_config.toml
  • src/a019_rename.sv
  • src/a019_pkg.sv

Reproduction Steps

  1. Extract A019.zip.
  2. Open the extracted A019 directory directly in VS Code.
  3. Set vizsla.scope.visibility to public.
  4. Reload or restart Vizsla, then wait until the workspace scan is complete.
  5. Open src/a019_rename.sv and src/a019_pkg.sv.
  6. Run Rename Symbol on PKG_VALUE in a019_pkg.sv, and rename it to PKG_RENAMED.
  7. Check .WIDTH(PKG_VALUE) in src/a019_rename.sv.

Actual Behavior

  • The PKG_VALUE declaration is renamed, but .WIDTH(PKG_VALUE) in a019_rename.sv is not updated.

Control observation from the same sample:

  • With default private scope visibility, renaming WIDTH only updates the declaration.
  • With public scope visibility, renaming WIDTH updates the named parameter override to .RENAMED_WIDTH(PKG_VALUE).
  • Therefore, scope.visibility = public is applied, but the imported package symbol usage is still missed.

Expected Behavior

  • Package symbol rename should update imported usages.

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