-
Notifications
You must be signed in to change notification settings - Fork 51
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
Split the remotetool into a separate library #568
Conversation
9600fa7
to
d6abb00
Compare
It sounds like you intend to import the new package from outside the |
ah, I intend to import the new package in reclient ( |
Ah, it looks like there is no inherent restrictions on importing from the cmd directory. The tooling only enforces that for internal packages: go.dev/doc/go1.4#internalpackages For the flags, it's not recommended to let packages define their own: https://google.github.io/styleguide/go/decisions#flags |
01cadfb
to
9e32ffd
Compare
In this CL, I'm creating an embeddedtool binary so that I can subsequently use it in reproxytool binary in re-client to implement the log file filtering functionalities. There's no behavior change associated with this CL. Tested: Ran show_action and show_action_2 (error'ed out) on the new remotetool.
9e32ffd
to
1241d14
Compare
Moved to pkg/tool as we discussed offline and got rid of the separate
Done! |
In this CL, I'm creating an embeddedtool binary so that I can subsequently use it in reproxytool binary in re-client to implement the log file filtering functionalities. There's no behavior change associated with this CL.
Tested: Ran show_action and show_action_2 (error'ed out) on the new remotetool.