It's extremely fast and covers a lot of random stuff that other linters don't seem to but which is still good practice. It can be a bit nitpicky but in a good way.
it's good! you don't need a pkg folder btw - they're not a go standard. check out `internal` as it's recognised by the tool chain and may be what you want
no stochastic parrots :D (well, I did ask LLMs some questions about scaffolding and doubts when it comes to std lib, but I always double check their answers, so for me it's not that huge time saving)
I've been a Gopher for over 8 years and a dev for over 25. I like asking LLMs for suggestions and improvements to my code. Sometimes they offer good insight, a lot of times they don't. No harm in testing!
Setting up golangci-lint doesn't need any work - just add the golangci-lint Github action to your project: https://github.com/golangci/golangci-lint-action
If you're looking to customize things, linter-wise, I would recommend configuring revive: https://github.com/mgechev/revive
It's extremely fast and covers a lot of random stuff that other linters don't seem to but which is still good practice. It can be a bit nitpicky but in a good way.
Thank you so much will dig into it!
Also you can run it directly (no need for npx envy)
go run github.com/fsgreco/go-bunny-sign/cmd/bunnysign@latest "hello world"
wait what! :O
It's a pretty good start, now add | (pipe) chars to either sides of the phrases, properly aligned and spaced to form a box.
mm yes that could be tricky but it's a good feature indeed
it's good! you don't need a pkg folder btw - they're not a go standard. check out `internal` as it's recognised by the tool chain and may be what you want
I struggled a bit with the scaffolding indeed, there are a lot of divergent opinions out there in the golang community
No button to punch the bunny?
(•ㅅ•) why so mean
zero deps, nice instructions, how nice
thank you :)
<sarcasm> What, no AI?!</sarcasm>
no stochastic parrots :D (well, I did ask LLMs some questions about scaffolding and doubts when it comes to std lib, but I always double check their answers, so for me it's not that huge time saving)
I've been a Gopher for over 8 years and a dev for over 25. I like asking LLMs for suggestions and improvements to my code. Sometimes they offer good insight, a lot of times they don't. No harm in testing!
Agree, if used with good sense then it's a really valid tool in the arsenal.