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

📝 clarify logger trace helper routing

Browse Source
This commit is contained in:
Nanaloveyuki
2026-06-14 11:23:34 +08:00
parent 9630c6cc3b
commit 5720ba6203
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/api/logger-trace.md
+5 -1
View File
@@ -37,7 +37,7 @@ Detailed rules explaining key parameters and behaviors
- This helper delegates to `log(Level::Trace, ...)`. - This helper delegates to `log(Level::Trace, ...)`.
- Trace is the lowest built-in severity and is often disabled in production. - Trace is the lowest built-in severity and is often disabled in production.
- Per-call target override is not exposed here; use `log(...)` if that is needed. - 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(...)`.
- Context, filtering, patching, and queue wrappers still apply through the logger sink chain. - Context, filtering, patching, and queue wrappers still apply through the logger sink chain.
### How to Use ### How to Use
@@ -62,6 +62,10 @@ logger.trace("cache probe", fields=[field("key", "user:42")])
In this example, trace output stays lightweight while still carrying structured detail. In this example, trace output stays lightweight while still carrying structured detail.
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.: