[FarhanAliRaza]

All Submissions:

• Have you followed the guidelines stated in CONTRIBUTING.md file?
• Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

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?

Problem

A str | None state var holding None crashed the page for every string operation that compiles to a native string method:

class S(rx.State):
    m: str | None = None

rx.foreach(S.m.split(" "), rx.text)   # TypeError: Cannot read properties of null (reading 'split')

split with a separator, strip / lstrip / rstrip, lower, upper, title, capitalize, contains, startswith, endswith, replace and * all threw, and the whole page fell into the error boundary. length, indexing, slicing and split() already read None as "" through the code point helpers, so the behaviour depended on which operation was used.

Fix

This takes option 1 from #7873 (treat None as "" everywhere), which is the rule #7800 already set for optional lists and sets.

StringVar gets the same _or_empty() view ArrayVar has: when the var type allows None, the operation reads (x ?? ""), typed without None. A string that cannot be None compiles exactly as before, with no guard. The operations that go through a null-safe helper (pyStrLength, pyStrAt, pyStrSlice, pyStrChars) are left unguarded.

Not changed: + / f-string concatenation and the comparison operators, which do not throw on null.

Tests

• tests/units/reflex_base/vars/test_sequence.py: the exact compiled JS of every guarded operation for an optional and a required string, the result types, and the helper-backed operations that stay unguarded.
• tests/integration/tests_playwright/test_var_operations.py: the existing app renders the operations on an optional string holding None and on one holding a value. Without the fix the page does not render at all (TypeError: Cannot read properties of null in the browser).

Ran locally: tests/units (one unrelated browser-launch test in reflex_bench cannot start Chromium in my sandbox), the two string Playwright modules, ruff check, ruff format, and pyright on the changed files.

closes #7873

https://claude.ai/code/session_01LwJUCTCgM7D4Vj6H4dRWss

---

Generated by Claude Code

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Summary

String methods now treat optional strings holding None as empty text rather than crashing the page.

• Optional string operations treat None as an empty string.

The previous documentation finding is fixed. No new issues found.

_{Reviews (3) · Last reviewed commit: "Skip the optional check for plain str va..." · Reviewed by Greptile}

[cubic-dev-ai]

2 issues found across 5 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/reflex-base/src/reflex_base/vars/sequence.py">

<violation number="1" location="packages/reflex-base/src/reflex_base/vars/sequence.py:786">
P2: Concatenation is still unguarded, so `None + "x"` renders as `"nullx"` in the browser. The new docs and news entry say an optional string holding `None` acts as `""` in every string operation, so guard `__add__` and `__radd__` with `_or_empty()` as the array `__add__` does. The ordering comparisons (`<`, `>`, `<=`, `>=`) have the same gap, so either guard them or narrow the docs claim.</violation>
</file>

<file name="docs/vars/var-operations.md">

<violation number="1" location="docs/vars/var-operations.md:490">
P3: Qualify these results with non-empty search arguments: `contains("")`, `startswith("")`, and `endswith("")` are true, while replacing `""` in `""` with `"x"` yields `"x"`. Apply the same qualification to the news fragment.</violation>
</file>

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

View guided diff | Turn on auto-fix | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: Concatenation is still unguarded, so None + "x" renders as "nullx" in the browser. The new docs and news entry say an optional string holding None acts as "" in every string operation, so guard __add__ and __radd__ with _or_empty() as the array __add__ does. The ordering comparisons (<, >, <=, >=) have the same gap, so either guard them or narrow the docs claim.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At packages/reflex-base/src/reflex_base/vars/sequence.py, line 786:

<comment>Concatenation is still unguarded, so `None + "x"` renders as `"nullx"` in the browser. The new docs and news entry say an optional string holding `None` acts as `""` in every string operation, so guard `__add__` and `__radd__` with `_or_empty()` as the array `__add__` does. The ordering comparisons (`<`, `>`, `<=`, `>=`) have the same gap, so either guard them or narrow the docs claim.</comment>

<file context>
@@ -783,6 +783,16 @@ def create(
 class StringVar(Var[STRING_TYPE], python_types=str):
     """Base class for immutable string vars."""
 
+    def _or_empty(self) -> StringVar[Any]:
+        """View an optional string as an empty string while it holds None.
+
</file context>

[FarhanAliRaza]

Narrowed the claim instead of guarding + (cbd9751): the docs and the news fragment now say the string methods read None as "", and name + and the comparison operators as not covered.

I left + alone on purpose. An f-string (f"{S.m} x") builds the same concatenation without going through __add__, so guarding __add__ / __radd__ would make S.m + " x" and f"{S.m} x" render differently for the same value. Neither throws, so it is outside what #7873 is about (operations that crash the page); changing what a None renders as in concatenation is a separate decision for both forms together.

---

Generated by Claude Code

[cubic-dev-ai]

P3: Qualify these results with non-empty search arguments: contains(""), startswith(""), and endswith("") are true, while replacing "" in "" with "x" yields "x". Apply the same qualification to the news fragment.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At docs/vars/var-operations.md, line 490:

<comment>Qualify these results with non-empty search arguments: `contains("")`, `startswith("")`, and `endswith("")` are true, while replacing `""` in `""` with `"x"` yields `"x"`. Apply the same qualification to the news fragment.</comment>

<file context>
@@ -487,6 +487,8 @@ def var_string_example():
     )

+An optional string var (str | None) holding None acts as an empty string in every string operation: lower, strip and replace give an empty string, contains and startswith are false, length is 0 and split(" ") gives [""], as it does for "".
+

Get Item (Indexing)

</file context>

</details>

[codspeed]

Merging this PR will not alter performance

1 warning

⚠️ 15 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

✅ 143 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing ccr-b5f6d6c1-k1ong5-optional-str-none (cbd9751) with main (8e5bb84)}

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. ↩