Replies: 1 comment 2 replies
-
The functions you listed are HTTP response functions, meaning that they're more of a pointer to a function. They implement an interface and have a signature that looks like this: They're called when the relevant endpoint is hit. Debugging is better done deeper inside. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Apologies, stupid question, but just poking at GO for the first time here.
How do you go about setting up the debug config?
I assume its something like this.
but the three arguments that go in.. what is expeceted to run it?
ServeGadget, UserInfo, DownloadURLCollector
I can compile it all fine, runs fine once compiled. But its rather... counterproductive way of doing it.
Any chanse you could help me out getting it running?
Trying to look into adding more filtering options. Such as filtering on tag names.
Beta Was this translation helpful? Give feedback.
All reactions