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
Fix pub warnings for tool package before publishing #146
Conversation
@kevmoo Note: I can fix those errors by moving the builder code out of |
Under the tool dir makes sense to me. These are not things that are needed at runtime on the users machine. |
The package isn't meant to just be a CLI -- it's meant to support other tools that can leverage it. The builder can't be exported if not under lib. |
Right...
Hrm...
Well, since it's globally installed, having these extra dependencies won't
block others either...unless they are building similar tools.
…On Wed, Dec 23, 2020 at 1:26 PM Tony Pujals ***@***.***> wrote:
The package isn't meant to just be a CLI -- it's meant to support other
tools that can leverage it. The builder can't be exported if not under lib.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#146 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAEFCV4JELKG5T7SIG76KDSWJN7PANCNFSM4VHN4GBA>
.
|
It could be refactored out into its own package, but that would take time. I figured this was the least amount of work to get this out today. |
It's fine, I can move it -- I just have to go through the cycle of rebuilding and getting presubmit checks to pass, etc. |
At some point, various tool package consumers (a CLI, Cloud Code, etc.) will be in their separate packages. I'll go ahead and refactor for now if that's your preference. Just going to take a bit longer than I wanted while working on docs today. Running against the clock now! :D |
@kevmoo PTAL |
Draft PR while I fix issues:
Just discovered pub warnings while working on the docs and realizing we hadn't published to pub.dev yet: