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
docs: move example inline into godoc #4626
Conversation
This change is needed, at least temporarily, to facilitate the splitting of modules. The parent module can't depend on a module that is about to be split out as tidying will fail to resolve import paths as the code no longer exists.
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 can't do a 2-step process to avoid this? Publish the new module then update the root module?
Co-authored-by: Tyler Bui-Palsulich <26876514+tbpg@users.noreply.github.com>
@tbpg I don't think so. Root module needs to be tagged first so that the sub-module can depend on it. Once tagged it can no longer reference the new child mods code without a new dependency on the child mod. I think we should avoid having the root depend on any gapic packages if possible. |
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.
Ah, got it. Thanks for the explanation.
This change is needed, at least temporarily, to facilitate the
splitting of modules. The parent module can't depend on a module
that is about to be split out as tidying will fail to resolve
import paths as the code no longer exists.