Skip to content

Remove limitation that isn't there anymore and add Development sectio… #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 24, 2022
Merged

Remove limitation that isn't there anymore and add Development sectio… #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,8 @@ Package variable reassignment is generally confusing, though, and we recommend a
The `pattern` flag can be set to a regular expression to define what variables cannot be reassigned, and `.*` is
recommended if it works with your code.

## Limitations
## Development

If a variable shadows the name of an import, an assignment of a field in the variable will trigger the linter. Shadowing
can be confusing, so it's recommended to rename the variable.
[mage](https://magefile.org/) is used for development. Run `go run mage.go -l` to see available targets.

For example, to run checks before sending a PR, run `go run mage.go check`.