From cc3d1b1f1c72713df6d5cfb08eccf3dbdb265c1c Mon Sep 17 00:00:00 2001 From: Nanaloveyuki Date: Sun, 14 Jun 2026 11:04:04 +0800 Subject: [PATCH] :memo: clarify library async info helper routing --- docs/api/library-async-logger-info.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/api/library-async-logger-info.md b/docs/api/library-async-logger-info.md index b26d6c1..9993a1b 100644 --- a/docs/api/library-async-logger-info.md +++ b/docs/api/library-async-logger-info.md @@ -41,6 +41,7 @@ Detailed rules explaining key parameters and behaviors - This helper delegates to `info(...)` on the wrapped async logger, which in turn uses `log(Level::Info, ...)`. - The record is still subject to min-level gating, stored shared context fields, patching, filtering, and overflow policy. +- This helper does not accept a per-call target override. It uses the facade's stored target unless the facade was derived earlier with `with_target(...)` or `child(...)`. - `Info` is often the default operational logging level for async application events. - Use this helper when explicit info intent is clearer than a raw `log(...)` call. - Async state helpers remain on the underlying `AsyncLogger[S]` and require `to_async_logger()` first. @@ -72,6 +73,8 @@ In this example, the record remains concise while still carrying useful metadata And any shared context fields already stored on the facade are still prepended before these per-call fields. +And the write still uses the facade's stored target because this shortcut does not take a one-off `target=` override. + ### Error Case e.g.: