From 73c924e9757ed024bc300324d818bf4a48549dc3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Vin=C3=ADcius=20Garcia?= Date: Tue, 18 Jul 2023 19:04:18 -0300 Subject: [PATCH] Updated Debugging with `ksql.InjectLogger` (markdown) --- Debugging-with-`ksql.InjectLogger`.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Debugging-with-`ksql.InjectLogger`.md b/Debugging-with-`ksql.InjectLogger`.md index 97385a9..d9c0daa 100644 --- a/Debugging-with-`ksql.InjectLogger`.md +++ b/Debugging-with-`ksql.InjectLogger`.md @@ -8,7 +8,7 @@ You can either decide to use one of the two built-in loggers, by using: Or you can create your own, by passing a custom function to InjectLogger, e.g.: ```golang -ctx := InjectLogger(ctx, func(ctx context.Context, values LogValues) { +ctx := ksql.InjectLogger(ctx, func(ctx context.Context, values LogValues) { fmt.Println("the values are:", values.Query, values.Params, values.Err) }) ```