add rx memo marker to memo fields

[adhami3310]

No description provided.

[linear]

ENG-7320 rx.memo with arguments that shadow js keywords does not work

[codspeed-hq]

CodSpeed Performance Report

Merging #5709 will not alter performance

_{Comparing khaleel/eng-7320-rxmemo-with-arguments-that-shadow-js-keywords-does-not-work (f10e241) with main (9b2d93e)}

Summary

✅ 8 untouched benchmarks

[greptile-apps]

Greptile Summary

This PR introduces a memo marker system to fix an issue where memoized components with arguments that shadow JavaScript keywords would fail to work properly. The changes add a new constant MEMO_MARKER with value '_rx_memo_' and systematically append this marker to all prop names in memoized components.

The core problem being solved is that when Reflex converts Python component prop names to JavaScript camelCase (e.g., for React components), prop names like 'class', 'default', 'for', 'function', etc. remain as JavaScript reserved words and cause syntax errors in the generated code. By appending the memo marker, these problematic names become safe variants (e.g., 'class' → 'classRxMemo', 'default' → 'defaultRxMemo').

The implementation involves:

1. Adding the MEMO_MARKER constant to reflex/constants/state.py following the established pattern of FIELD_MARKER
2. Modifying CustomComponent._post_init in reflex/components/component.py to append the marker when creating event triggers and processing camel-cased prop names for memoized components
3. Updating test files to reflect the new expected behavior where memoized component props have the 'RxMemo' suffix

This change integrates cleanly with the existing component system's marker-based approach for distinguishing different types of component properties during code generation. The marker helps the compiler identify and handle memoized arguments correctly while ensuring JavaScript keyword conflicts are avoided.

Confidence score: 4/5

• This PR addresses a specific JavaScript keyword conflict issue with a targeted solution that follows established patterns in the codebase
• Score reflects solid implementation but potential edge cases around complex prop handling and the systematic nature of the string appending approach
• Pay close attention to the component.py changes in CustomComponent._post_init method where the marker logic is implemented

_{4 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}