Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add tip about being able to log and debug a bunch of variables without the formatting hassle #162

Merged
merged 2 commits into from
Jul 23, 2021
Merged

Add tip about being able to log and debug a bunch of variables without the formatting hassle #162

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
004eb29
Add tip about being able to debug a bunch of variables without format…
MadLittleMods Jul 15, 2021
d271c60
Merge branch 'master' into madlittlemods/use-logrus-tip
MadLittleMods Jul 20, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions ONBOARDING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,6 +163,14 @@ There is no syntactically pleasing way to do this. Create a separate function wh

This is done using standard Go testing mechanisms, use `t.Logf(...)` which will be logged only if the test fails or if `-v` is set. Note that you will not need to log HTTP requests performed using one of the built in deployment clients as they are already wrapped in loggers. For full HTTP logs, use `COMPLEMENT_DEBUG=1`.

For debugging, you can also use `logrus` to expand a bunch of variables:

```go
logrus.WithFields(logrus.Fields{
"events": events,
"context": context,
}).Error("message response")
```

### How do I show the server logs even when the tests pass?

Expand Down