You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When generating the cppcheck.xml file at the root of the workspace and setting the pattern to 'cppcheck\.xml' the plugin did not find the file. I had to set the pattern to '.*/*cppcheck\.xml$' to find it which took me some time.
Is it possible to change it or document it ?
Also for diagnostic it would help to log the name (or number) of file found as the log "Found 0 violations from ViolationConfig [reporter=CPPCHECK..." doesn't indicate if there was an empty file or if no file was found.
Thanks for the great plugin !
The text was updated successfully, but these errors were encountered:
Thanks for the feedback.
Yes I did notice this text, but assumed that the initial ".*/" was for the "anywhere" condition and was not needed for a file located at root.
Good to know for the "fine" logs.
Anyway that's working nice for me now that it's configured correctly, adding those info in the doc could help some others ;)
When generating the cppcheck.xml file at the root of the workspace and setting the pattern to 'cppcheck\.xml' the plugin did not find the file. I had to set the pattern to '.*/*cppcheck\.xml$' to find it which took me some time.
Is it possible to change it or document it ?
Also for diagnostic it would help to log the name (or number) of file found as the log "Found 0 violations from ViolationConfig [reporter=CPPCHECK..." doesn't indicate if there was an empty file or if no file was found.
Thanks for the great plugin !
The text was updated successfully, but these errors were encountered: