-
Notifications
You must be signed in to change notification settings - Fork 64
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
Ability to run go-pry outside of main package #19
Comments
Yeah, it'd be definitely nice to support non-main packages. Since go-pry
works by injecting code you'd either have to specify the package or do a
very expensive scan of the entire dependency tree.
…On Tue, Jul 11, 2017, 13:13 Catherine Cai ***@***.***> wrote:
I'm wondering if it's in the scope of go-pry to eventually allow it to run
in non-main packages. The way I currently have my Go project set up is to
have a main package that sources certain functionalities from a ton of
subpackages.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#19>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA3fMMzEljNTtKRZfEB-EzWPohLztCqCks5sM9dqgaJpZM4OUwSv>
.
|
Sub packages within the same directory should work however
…On Tue, Jul 11, 2017, 15:09 Tristan Rice ***@***.***> wrote:
Yeah, it'd be definitely nice to support non-main packages. Since go-pry
works by injecting code you'd either have to specify the package or do a
very expensive scan of the entire dependency tree.
On Tue, Jul 11, 2017, 13:13 Catherine Cai ***@***.***>
wrote:
> I'm wondering if it's in the scope of go-pry to eventually allow it to
> run in non-main packages. The way I currently have my Go project set up is
> to have a main package that sources certain functionalities from a ton of
> subpackages.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#19>, or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA3fMMzEljNTtKRZfEB-EzWPohLztCqCks5sM9dqgaJpZM4OUwSv>
> .
>
|
Hi @d4l3k thx for you great project. |
There's currently no way, but it jwould make a lot of sense to add a new flag to specify extra packages to pry into. Like |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm wondering if it's in the scope of go-pry to eventually allow it to run in non-main packages. The way I currently have my Go project set up is to have a main package that sources certain functionalities from a ton of subpackages.
The text was updated successfully, but these errors were encountered: