Remove stale rich-markup escapes leaking backslashes into logged warnings

[masenf]

Type of change

• Bug fix (non-breaking change which fixes an issue)

Changes To Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

Defect

FINDING-027 from 0.9.9a1 pre-release testing (cosmetic regression vs 0.9.8, verifier-confirmed): compile-time warnings print literal backslash-escaped brackets, e.g. the event-handler arg-mismatch warning renders as

Warning: Event handler on_submit expects (dict\[str, typing.Any]) -> () but got (dict\[str, str]) -> () ...

where 0.9.8 printed clean dict[str, ...].

Root cause: 0.9.8 built these messages with rich-markup escaping (rich.markup.escape() / .replace("[", "\\[")) and emitted them via the legacy console.* helpers, whose rich Console rendered with markup enabled and consumed the \[ escapes. The 0.9.9 migration to the stdlib logging pipeline kept the escaping, but RichConsoleHandler.emit renders records with markup=False unless a record opts in via extra={"rich": True} (these call sites do not), so the escapes now print literally — in the console sink, the JSON sink, and the full-logging file.

Fix

Drop the stale escaping at every call site that logs through the pipeline without the markup opt-in (all confirmed to use console.* + escaping on the v0.9.8 tag, i.e. all the same migration regression):

• reflex_base/event/__init__.py — the arg-mismatch warning from the finding's repro (.replace("[", "\\[") on both type lists)
• reflex_base/components/component.py — None-to-non-Optional Var deprecation warning
• reflex_base/vars/base.py — computed var return-type error
• reflex_base/event/processor/event_processor.py — event-queue processing error ([txid=...])
• reflex/state.py — inline computed var type warning and state field type error

Bracketed text now renders verbatim. Markup injection from user-controlled values (type names, event payloads) stays impossible: the sink keeps markup=False, nothing opts into markup rendering. Call sites that do opt in via extra={"rich": True} (e.g. js_runtimes.py, prerequisites.py) correctly keep their escaping and are untouched, as is the deliberate escaping of client-supplied JS error text placed into Exception objects for user-defined frontend exception handlers.

Test plan

• New regression test tests/units/test_event.py::test_arg_mismatch_warning_renders_brackets_verbatim: reproduces the finding's scenario (handler annotated dict[str, str] bound to the on_submit specs) through the managed pipeline and asserts the captured rendered output contains expects (dict[str, typing.Any]) -> () but got (dict[str, str]) -> () with no backslashes. Fails on unfixed main with dict\[str, typing.Any] in the output; passes with the fix.
• New injection-safety test tests/units/reflex_base/utils/test_log.py::test_warning_with_markup_tags_stays_literal: a warning containing [red]x[/red] renders it literally — neither styled/stripped nor escaped.
• uv run ruff check . and uv run ruff format . clean; uv run pyright reflex tests passes (0 errors); pyright over reflex_base shows only a pre-existing warning unrelated to this change.
• Scoped suites pass: tests/units/test_event.py, tests/units/reflex_base/utils/test_log.py, tests/units/reflex_base/event/processor/test_event_processor.py, tests/units/components/test_component.py, tests/units/test_state.py, tests/units/test_var.py, tests/units/vars. (One pre-existing cross-file ordering failure, test_superseding_event_logs_debug_on_cancel when test_log.py runs before test_event_processor.py in the same invocation, reproduces identically on unmodified main and is unrelated.)

🤖 Generated with Claude Code

https://claude.ai/code/session_01EMjBXPozsNeQNSBZecNH8x

---

Generated by Claude Code

[greptile-apps]

Greptile Summary

This PR removes obsolete Rich-markup escaping from warnings, errors, and VarAttributeError messages now rendered by the plain stdlib logging pipeline.

• Preserves literal brackets in event, state, component, and computed-var diagnostics.
• Adds regression coverage for bracket rendering and markup-like text.
• Adds release-note fragments for the root and reflex-base packages.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
packages/reflex-base/src/reflex_base/event/init.py	Removes stale bracket escaping from event-handler argument mismatch warnings while retaining the existing validation behavior.
packages/reflex-base/src/reflex_base/event/processor/event_processor.py	Logs event-queue failures verbatim through the non-markup logging path.
packages/reflex-base/src/reflex_base/components/component.py	Removes Rich escaping from the None-to-non-Optional deprecation warning.
packages/reflex-base/src/reflex_base/vars/base.py	Removes obsolete escaping from computed-var diagnostics and attribute errors.
packages/reflex-base/src/reflex_base/vars/object.py	Preserves generic type brackets verbatim in object-var attribute errors.
reflex/state.py	Removes obsolete escaping from inline computed-var and state-field type diagnostics.
tests/units/reflex_base/utils/test_log.py	Verifies that markup-like warning text remains literal when records do not opt into Rich rendering.
tests/units/test_event.py	Adds end-to-end regression coverage for clean bracket rendering in argument mismatch warnings.

_{Reviews (3): Last reviewed commit: "Remove test asserting on the dropped mar..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 32 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing claude/rel-fix-warning-escape-leak (eeba048) with main (7427617)}

Footnotes

1. 8 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[cubic-dev-ai]

All reported issues were addressed across 8 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[masenf]

@FarhanAliRaza thanks — both VarAttributeError sites are now de-escaped on this branch (the source change landed in 0b16599/d5e0344), and 2ec0993 adds your suggested regression test (tests/units/test_var.py::test_var_attribute_error_renders_brackets_verbatim), verified to fail against the pre-fix sources and pass with them. The news fragments mention the VarAttributeError messages as well.

---

Generated by Claude Code