-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'is_third_party' does not disable errors in third party libraries #366
Comments
The |
@JakubFranek, you can't use glob expressions to include all of the VHDL files from within the VUnit distribution, because some of them (or many of them) conflict (note the error messages "A primary unit has already been declared..."). One alternative is to export your VUnit file list and use the It would be great if VHDL-LS gave us an |
This was discussed in #40, but only include was added. It would be great to have an exclude list too, especially for Vunit! |
Hello
I am using vhdl-ls linter via TerosHDL integration in VS Code. I have a
vhld_ls.toml
file like this in the root of my repository:Adding
vunit_lib
like this was the only way I found to have vhdl-ls recognizevunit_lib
usage within my testbenches successfully.My expectation is that the
vunit_lib.is_third_party = true
statement will supress all errors withinvunit_lib
.The reality is hundreds of errors, all in
vunit_lib
:Is this a bug, working as intened, or is there perhaps a different way to ignore/supress/exclude errors in a particular folder?
I find this behavior very annoying. If I don't include
vunit_lib
files, I get errors in my testbench, if I do, I get errors invunit_lib
itself.Thank you.
Kind regards
Jakub
The text was updated successfully, but these errors were encountered: