flipt
golangci-lint
Our great sponsors
flipt | golangci-lint | |
---|---|---|
19 | 72 | |
3,314 | 14,427 | |
3.3% | 2.1% | |
9.9 | 9.7 | |
3 days ago | 4 days ago | |
Go | Go | |
GNU General Public License v3.0 only | 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.
flipt
-
Ask HN: How did you build feature flags?
We at https://flipt.io are putting on a buy vs build webinar in a couple of weeks to discuss this very thing as it's a common question that engineering teams seem to have.
If you're interested in attending its taking place on LinkedIn on April 17: https://www.linkedin.com/events/buildvs-buy-pickingafeaturef...
-
Open Policy Agent
We're currently evaluating OPA for adding RBAC to our open-source application [0]. We plan on using the Go API [1] and doing the policy eval directly in our app since our app is also written in Go.
The thinking is we'll have some basic built-in policies (like admins can do X, editors can do Y, etc) but also allow users to configure their own policies if they want by writing rego and loading their policy rules at startup time (via config). We'd document the inputs that we pass to the evaluation call such as request headers, IP, role, etc.
I'm curious if anyone has ever tried something like this or similar?
[0] https://github.com/flipt-io/flipt
[1] https://www.openpolicyagent.org/docs/latest/integration/#int...
-
GitHub issues from top Open Source Golang Repositories that you should contribute to
Flipt - Clickhouse integration for flag eval analytics
-
οΈππ Top 3 DevOps Trends to Watch Out for in 2024 π
At Flipt, we continually discuss technologies that can bring change to the industry. In this article, we delve into cutting-edge top trends and tools that can redefine DevOps and platform engineering this year.
-
οΈππ 3 Must Know Tools for Top DevOps Engineers π·
In this article, I will share the DevOps tools that we've used at Flipt and in previous roles (such as at InfluxDB). These tools are relevant for any modern software project.
-
οΈπ¨βπ§ 3 Tiny Fixes You Can Make To Start Contributing to Any Open Source Project π
But after onboarding 50+ contributors to Flipt, I realized there are ways to make starts easy for newbies.
-
π₯ The Single Best Tip To Attract More Contributors To Your GitHub Projectπ‘
In this article, I will share the effort-based issue labeling system we use at Flipt to deal with this problem.
-
3 Basic Traits That Every Successful Open Source Developer Has
Flipt has reached 3k GitHub stars β this week.
-
Save 500+ Hours of Maintenance Work With These 3 GitHub Actions
In this article, Iβm sharing 3 GitHub Actions we use at Flipt that saved us more than 500 developer hours.
-
3 Best Code Quality Tools For Your Open Source Project
In this article, Iβll share 3 tools we use at Flipt to maintain high code quality and ship features reliably.
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?
Flagr - Flagr is a feature flagging, A/B testing and dynamic configuration microservice
ireturn - Accept Interfaces, Return Concrete Types
nginx-prometheus - Turn Nginx logs into Prometheus metrics
gosec - Go security checker
flagsmith - Open Source Feature Flagging and Remote Config Service. Host on-prem or use our hosted version at https://flagsmith.com/
golangci-lint-action - Official GitHub action for golangci-lint from its authors
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
gopl.io - Example programs from "The Go Programming Language"
nsq - A realtime distributed messaging platform
go - The Go programming language
traefik - The Cloud Native Application Proxy
ls-lint - An extremely fast directory and filename linter - Bring some structure to your project filesystem