rewrite sqlvet using analysis.Analyzer?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 500
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the current sqlvet implementation to understand how it parses entire main packages, then review the linked article about Go vet's analysis.Analyzer framework. Determine whether the analyzer approach can preserve SQL detection while avoiding full-package parsing; done means an agreed rewrite scope and evidence that large codebases are handled more efficiently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100