Closed rahultadak closed 2 days ago
Thanks for the report! This should be fixed in the most recent update, please let me know if it works for you! One note: because the filesystem glob is used instead of vscode's, the .{svh,sv} syntax doesn't work, or at least for the OS I tested on.
Thanks for the fix. I was looking at the VSCode API and found the asRelativePath
call in the workspace
namespace. Would that be a better fix here instead of the if-else fix you made?
No that won't really help, it just returns the same path, I believe either because it's a glob or because it's outside of the workspace. The documentation on that function isn't too clear, it seems to contradict itself
It seems that the extension parses the include globs and expects the paths provided in the include globs to be inside the workspace always. This is not necessarily the case in projects where we refer to external IPs.
Environment
{ "verilog.ctags.indexAllIncludes": true, "verilog.excludeGlob": "**/work/*", "verilog.lint.slang.path": "slang", "verilog.lint.slang.args": "--error-limit 200", "verilog.svFormat.verible.path": "verible-verilog-format", "verilog.ctags.path": "ctags", "verilog.includeGlobs": [ "/path/to/uvm-1.2/*.{sv,svh}", ], }
Steps to reproduce:
Logs: (Get logs from Output > verilog)