Skip to content

feat(logging): add minimum level to in-memory logger - #273

Merged
David-patrick-chuks-02 merged 2 commits into
Lilly-Protocol:mainfrom
alexsmolya:bounty/issue-266-memory-logger-level
Sep 6, 2026
Merged

feat(logging): add minimum level to in-memory logger#273
David-patrick-chuks-02 merged 2 commits into
Lilly-Protocol:mainfrom
alexsmolya:bounty/issue-266-memory-logger-level

Conversation

@alexsmolya

Copy link
Copy Markdown
Contributor

Summary

  • InMemoryRuntimeLogger previously recorded every supported level with no configurable threshold.
  • It now accepts optional level?: RuntimeLogLevel.
  • The default remains debug, preserving existing all-level recording.
  • Explicit thresholds share the existing priority semantics used by ConsoleRuntimeLogger.
  • Filtering occurs before capacity eviction and append.
  • InMemoryRuntimeLoggerOptions is publicly exported.

Validation

  • Focused logger suite: 29/29 passed.
  • Full npm run verify: 231/231 tests passed with coverage thresholds.
  • Format, lint, typecheck, build, and git diff --check passed.

Fixes #266

@David-patrick-chuks-02
David-patrick-chuks-02 merged commit da2505d into Lilly-Protocol:main Sep 6, 2026
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bounty: $60] Give InMemoryRuntimeLogger a configurable minimum level matching ConsoleRuntimeLogger

3 participants