Skip to content

docs(readme): point the log-level limitation at filterLogger - #98

Merged
kkdev92 merged 1 commit into
mainfrom
docs/readme-log-level
Oct 3, 2026
Merged

kkdev92 merged 1 commit into
mainfrom
docs/readme-log-level

Conversation

@kkdev92

@kkdev92 kkdev92 commented Oct 3, 2026

Copy link
Copy Markdown
Owner

The README's Known Limitations entry on log levels now ends by pointing at filterLogger.

Why

The entry says two things:

  • the framework does not filter by log level, and leaves the level to VS Code;
  • an extension's own log-level setting can only make the log quieter.

It stopped there. With filterLogger exported, that reads as if nothing helps with such a setting. The framework itself still writes everything, so the first half stands unchanged. The entry now adds that filterLogger applies such a setting to the loggers an extension hands out.

Changes

  • README.md: one clause at the end of the entry.

No code changes.

🤖 Generated with Claude Code

The Known Limitations entry says the framework does not filter by log level,
and that a log-level setting of an extension's own can only make the log
quieter. It stopped there, which now reads as if nothing helps with that
setting. `filterLogger` does, so the entry says so; the framework itself
still writes everything and leaves the level to VS Code.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kkdev92
kkdev92 merged commit f502518 into main Oct 3, 2026
10 checks passed
@kkdev92
kkdev92 deleted the docs/readme-log-level branch October 3, 2026 11:48
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.

1 participant