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
- Extract
A019.zip.
- Open the extracted
A019 directory directly in VS Code.
- Set
vizsla.scope.visibility to public.
- Reload or restart Vizsla, then wait until the workspace scan is complete.
- Open
src/a019_rename.sv and src/a019_pkg.sv.
- Run Rename Symbol on
PKG_VALUE in a019_pkg.sv, and rename it to PKG_RENAMED.
- 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.
Rename misses package import usage even when scope visibility is public
A019.zip
Environment
v0.1.2vizsla 0.1.0_RELEASE+43c5ed5.20260521T023910ZAttachment
Please use the attached
A019.zip. Extract it, then open the extractedA019directory directly in VS Code as the workspace root.Source files:
vizsla_config.tomlsrc/a019_rename.svsrc/a019_pkg.svReproduction Steps
A019.zip.A019directory directly in VS Code.vizsla.scope.visibilitytopublic.src/a019_rename.svandsrc/a019_pkg.sv.PKG_VALUEina019_pkg.sv, and rename it toPKG_RENAMED..WIDTH(PKG_VALUE)insrc/a019_rename.sv.Actual Behavior
PKG_VALUEdeclaration is renamed, but.WIDTH(PKG_VALUE)ina019_rename.svis not updated.Control observation from the same sample:
privatescope visibility, renamingWIDTHonly updates the declaration.publicscope visibility, renamingWIDTHupdates the named parameter override to.RENAMED_WIDTH(PKG_VALUE).scope.visibility = publicis applied, but the imported package symbol usage is still missed.Expected Behavior