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
The current sqlvet requires full parsing of the entire main package(s), so it becomes pretty slow for a large codebase. There's conveniently an article about using "go vet"'s analysis.Analyzer framework to detect SQL statements:
Well, we sometimes want to check just a specific set of files. For example, we are using this tool in a git pre-commit hook. In such a case, it's better to check only the changed files.
The current sqlvet requires full parsing of the entire main package(s), so it becomes pretty slow for a large codebase. There's conveniently an article about using "go vet"'s analysis.Analyzer framework to detect SQL statements:
https://agniva.me/vet/2019/01/21/vet-analyzer.html
Does it make sense to rewrite sqlvet using it? I can try my hand over the holidays if you think it's a good idea.
The text was updated successfully, but these errors were encountered: