-
Notifications
You must be signed in to change notification settings - Fork 105
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.
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
tools: Move to a submodule #78
Conversation
Renaming tools.go to tools_test.go isn't enough. These constraints are still carried over to consumers. Renaming only drops them from `go mod vendor`. This moves tools dependencies to a `tools` submodule which we will never publish. Ref uber-go/multierr#38
Codecov Report
@@ Coverage Diff @@
## master #78 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 14 14
Lines 239 239
=========================================
Hits 239 239 Continue to review full report at Codecov.
|
@@ -8,6 +8,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 | |||
### Changed | |||
- Disallow incorrect comparison of atomic values in a non-atomic way. | |||
|
|||
### Removed | |||
- Remove dependency on `golang.org/x/{lint, tools}`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or maybe just Moved out test dependencies
(since it doesn't affect module resolution etc, just go mod download
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're not dropping all test dependencies, though. Only dev-time dependencies.
Move lint dependencies to a tools submodule so that these are not introduced as dependencies of the package. In other projects, we experimented with renaming `tools.go` to `tools_test.go` but that wasn't enough either. The tools submodule appears to be the safest approach. Supersedes #32 Refs uber-go/atomic#78
Move lint dependencies to a tools submodule so that these are not introduced as dependencies of the package. In other projects, we experimented with renaming `tools.go` to `tools_test.go` but that wasn't enough either. The tools submodule appears to be the safest approach. Supersedes #32 Refs uber-go/atomic#78
Move lint dependencies to a tools submodule so that these are not introduced as dependencies of the package. In other projects, we experimented with renaming `tools.go` to `tools_test.go` but that wasn't enough either. The tools submodule appears to be the safest approach. Supersedes #32 Refs uber-go/atomic#78
Renaming tools.go to tools_test.go isn't enough. These constraints are
still carried over to consumers. Renaming only drops them from
go mod vendor
.This moves tools dependencies to a
tools
submodule which we will neverpublish.
Ref uber-go/multierr#38