glsp
golangci-lint
glsp | golangci-lint | |
---|---|---|
4 | 72 | |
129 | 14,512 | |
- | 1.5% | |
5.2 | 9.7 | |
about 2 months ago | 2 days ago | |
Go | Go | |
Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
glsp
-
fe: A tiny, embeddable language implemented in ANSI C
I wrote a lisp, a while back, and then later added an LSP for it.
Since lisp is so simple in terms of syntax what I really did was tab-completion, and info-on-hover, for the built-in functions like "car", "cdr", and the primitives I added as part of a more complex standard-library.
In my case I was writing in go and I found an LSP-server package which was trivial to use. So getting the integration with emacs, vim, etc, was really trivial:
https://github.com/tliron/glsp
-
How to get into Language Server Protocol? Any good tutorials?
For Go I use this library. If you want examples for Go, you can have a look at the github-dependents of the library.
-
Language server for golangci-lint
Built on the excellent glsp package and heavily inspired by golangci-lint-langserver, this is a language server for golangci-lint.
-
How to create a language server (LSP) in Go?
I'm using https://github.com/tliron/glsp which works pretty good for me together with the official specification of the ls-protocol
golangci-lint
- makefile para projetos em Go
-
Finding unreachable functions with deadcode – The Go Programming Language
One of the checkers in golangci-lint does this. I forget which one.
golangci-lint rolls up lot of linters and checkers into a single binary.
There is a config file too.
https://github.com/golangci/golangci-lint
-
Using Private Go Modules with golangci-lint in GitHub Actions
golangci-lint is an amazing open-source tool for CI in Go projects. Basically, it's an aggregator and a Go linters runner that makes life easier for developers. It includes all the well-known liners by default but also provides an easy way to integrate new ones.
-
️👨🔧 3 Tiny Fixes You Can Make To Start Contributing to Any Open Source Project 🚀
Fun fact: We actually use a code linter via golangci-linter to catch misspellings in code/comments using client9/misspell.
-
Show HN: Error return traces for Go, inspired by Zig
The "standard linter" in Go is https://golangci-lint.run/ , which includes [1] the absolutely-vital errcheck which will do that for you.
For an Advent of Code challenge you may want to turn off a lot of other things, since the linter is broadly tuned for production, public code by default and you're creating burner code and don't care whether or not you have godoc comments for your functions, for instance. But I suggest using golangci-lint rather than errcheck directly because there's some other things you may find useful, like ineffassign, exportloopref, etc.
[1]: https://golangci-lint.run/usage/linters/
-
Hacking Go to give it sum types
golangci-lint recently integrated go-check-sumtype. I recommend using golangci-lint as a pre-commit hook, but if you're in a real hurry you can replace "go build" with a shell script that runs go-check-sumtype instead. This is probably better than a weird hack, not that you're saying that the weird hack is a good idea anyhow.
-
Building RESTful API with Hexagonal Architecture in Go
Golangci-lint is a tool for checking Go code quality, finding issues, bugs, and style problems. It helps keep the code clean and maintainable.
-
Structured Logging with Slog
This is such an infuriating problem. I'm convinced I'm using Go wrong, because I simply can't understand how this doesn't make it a toy language. Why the $expletive am I wasting 20-30 and more minutes per week of my life looking for the source of an error!?
Have you seen https://github.com/tomarrell/wrapcheck? It's a linter than does a fairly good job of warning when an error originates from an external package but hasn't been wrapped in your codebase to make it unique or stacktraced. It comes with https://github.com/golangci/golangci-lint and can even be made part of your in-editor LSP diagnostics.
But still, it's not perfect. And so I remain convinced that I'm misunderstanding something fundamental about the language because not being able to consistently find the source of an error is such an egregious failing for a programming language.
- golangci-lint 1.54.0 is released
- Seeking Insights: Tools Used in GitHub Actions for Security Code Checks and Vulnerability Detection
What are some alternatives?
golangci-lint-langserver - golangci-lint language server
ireturn - Accept Interfaces, Return Concrete Types
bass - a low fidelity scripting language for project infrastructure
gosec - Go security checker
python-language-server - An implementation of the Language Server Protocol for Python
golangci-lint-action - Official GitHub Action for golangci-lint from its authors
fe - A tiny, embeddable language implemented in ANSI C
gopl.io - Example programs from "The Go Programming Language"
DaedalusLanguageServer - A LanguageServer implementation in GO for the scripting language daedalus
go - The Go programming language
pygls - A pythonic generic language server
ls-lint - An extremely fast directory and filename linter - Bring some structure to your project filesystem