When using other linting plugins in VSCode, a file's problems are removed from the problems list when the file is closed in VSCode (for example with Pylint and the Python plugin). With VHDL-Tool, problems are left in the problems view from when a file is opened until VSCode is restarted.
When using other linting plugins in VSCode, a file's problems are removed from the problems list when the file is closed in VSCode (for example with Pylint and the Python plugin). With VHDL-Tool, problems are left in the problems view from when a file is opened until VSCode is restarted.
I think VSCode should really be responsible for removing problems from closed files.
However, I have worked around this by sending an empty problems list for the file when it is closed. This will be in version 0.5.
I think VSCode should really be responsible for removing problems from closed files.
However, I have worked around this by sending an empty problems list for the file when it is closed. This will be in version 0.5.
When using other linting plugins in VSCode, a file's problems are removed from the problems list when the file is closed in VSCode (for example with Pylint and the Python plugin). With VHDL-Tool, problems are left in the problems view from when a file is opened until VSCode is restarted.
I think VSCode should really be responsible for removing problems from closed files.
However, I have worked around this by sending an empty problems list for the file when it is closed. This will be in version 0.5.