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

📝 clarify default target snapshot semantics

Browse Source
This commit is contained in:
Nanaloveyuki
2026-06-14 12:05:28 +08:00
parent cf23bb6dbe
commit 04f7742238
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/api/set-default-target.md
+6 -1
View File
@@ -36,6 +36,7 @@ Detailed rules explaining key parameters and behaviors
- The function updates the internal `Ref[String]` used by `default_logger()`. - The function updates the internal `Ref[String]` used by `default_logger()`.
- It does not mutate any custom `Logger` values created earlier. - It does not mutate any custom `Logger` values created earlier.
- Later global writes inherit the new target unless a different explicit logger path is used. - Later global writes inherit the new target unless a different explicit logger path is used.
- Any explicit logger value that was already created earlier keeps the target it captured at creation time.
- This is useful when one application wants the convenience of global helpers while still labeling records consistently. - This is useful when one application wants the convenience of global helpers while still labeling records consistently.
### How to Use ### How to Use
@@ -62,6 +63,8 @@ warn("running fallback path")
In this example, later global writes stay grouped under the migration target. In this example, later global writes stay grouped under the migration target.
Earlier explicit logger values still keep whatever default target they captured before this change.
### Error Case ### Error Case
e.g.: e.g.:
@@ -73,5 +76,7 @@ e.g.:
1. This API is best suited for small apps, scripts, or a single shared logging entry path. 1. This API is best suited for small apps, scripts, or a single shared logging entry path.
2. Prefer explicit child or per-component loggers when target structure needs to vary across subsystems. 2. Call `default_logger()` again after changing the default if a fresh explicit logger value should reflect the new target.
3. Prefer explicit child or per-component loggers when target structure needs to vary across subsystems.