naloveyuki/BitLogger
1
0
Fork 0
mirror of https://github.com/Nanaloveyuki/BitLogger.git synced 2026-07-31 15:34:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

📝 clarify logger debug helper routing

Browse Source
This commit is contained in:
Nanaloveyuki
2026-06-14 11:22:15 +08:00
parent 6eec61eb2d
commit 9630c6cc3b
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/api/logger-debug.md
+5 -1
View File
@@ -37,7 +37,7 @@ Detailed rules explaining key parameters and behaviors
- This helper delegates to `log(Level::Debug, ...)`. - This helper delegates to `log(Level::Debug, ...)`.
- Debug logging is useful for development diagnostics that are usually too verbose for normal production visibility. - Debug logging is useful for development diagnostics that are usually too verbose for normal production visibility.
- Per-call target override is not exposed here; use `log(...)` for that level of control. - This helper does not accept a per-call target override. It uses the logger's stored target unless the logger was derived earlier with `with_target(...)` or `child(...)`.
- All logger wrappers remain active exactly as they would for the base `log(...)` path. - All logger wrappers remain active exactly as they would for the base `log(...)` path.
### How to Use ### How to Use
@@ -62,6 +62,10 @@ logger.debug("session loaded", fields=[field("user_id", "42")])
In this example, the logger emits structured state without using the fully explicit `log(...)` form. In this example, the logger emits structured state without using the fully explicit `log(...)` form.
And any shared context already carried by the logger still participates through the sink pipeline.
The write still uses the logger's stored target because this shortcut does not take a one-off `target=` override.
### Error Case ### Error Case
e.g.: e.g.: