eeafj/golangci-lint
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 1 Wiki Activity

Update README.md

Browse Source
This commit is contained in:
golangci 2018-05-26 08:36:09 +03:00 committed by GitHub
parent 327e4aed59
commit 2e1149af9b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@ -386,12 +386,13 @@ Thanks to developers and authors of used linters:
- [dominikh/go-tools/megacheck](https://github.com/dominikh/go-tools/tree/master/cmd/megacheck) - [dominikh/go-tools/megacheck](https://github.com/dominikh/go-tools/tree/master/cmd/megacheck)
# Future Plans # Future Plans
1. Fully integrate all used linters: make common interface and reuse 100% of what can be reused: AST traversal, packages preparation etc. 1. Upstream all changes of forked linters.
2. Make it easy to write own linter/checker: it should take minimum code, have perfect documentation, debugging and testing tooling. 2. Fully integrate all used linters: make common interface and reuse 100% of what can be reused: AST traversal, packages preparation etc.
3. Speedup packages loading (dig into [loader](golang.org/x/tools/go/loader)): on-disk cache and existing code profiling-optimizing. 3. Make it easy to write own linter/checker: it should take minimum code, have perfect documentation, debugging and testing tooling.
4. Analyze (don't only filter) only new code: analyze only changed files and dependencies, make incremental analysis, caches. 4. Speedup packages loading (dig into [loader](golang.org/x/tools/go/loader)): on-disk cache and existing code profiling-optimizing.
5. Smart new issues detector: don't print existing issues on changed lines. 5. Analyze (don't only filter) only new code: analyze only changed files and dependencies, make incremental analysis, caches.
6. Integration with Text Editors. On-the-fly code analysis for text editors: it should be super-fast. 6. Smart new issues detector: don't print existing issues on changed lines.
7. Minimize false-positives by fixing linters and improving testing tooling. 7. Integration with Text Editors. On-the-fly code analysis for text editors: it should be super-fast.
8. Automatic issues fixing (code rewrite, refactoring) where it's possible. 8. Minimize false-positives by fixing linters and improving testing tooling.
9. Documentation for every issue type. 9. Automatic issues fixing (code rewrite, refactoring) where it's possible.
10. Documentation for every issue type.