generated app directory fails linting with golangci-lint
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 175
- PR merge metrics
- No merged PRs in 30d
Description
```
golangci-lint run --fix
bud/internal/app/main.go:74:19: Error return value of `budClient.Publish` is not checked (errcheck)
budClient.Publish("app:ready", nil)
```
As part of CI I run a linting of my repository. I suggest adding the line `//nolint` at the top of the template for `bud/internal/app/main.go`, as well as any other bud-managed template boilerplate files. This way any linters people use will ignore these files (without having to do special configuration to exclude the `bud` directory like is already automagically done in the `.gitignore`.)
Contributor guide
No contributing guide indexed for this repository
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 with the generated bud/internal/app/main.go template and reproduce the report using golangci-lint run --fix. Review the related bud-managed template boilerplate and .gitignore context; done means generated files no longer trigger the reported errcheck lint without requiring repository-specific exclusions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100