v0.2.3

v0.2.3 — Release Notes

🐛 Bug Fix

SSR props no longer break JSON.parse on pages containing <!-- or -->

The inline-JSON escaper (pyxle.ssr._escape.escape_inline_json) previously rewrote HTML-comment sequences with backslash escapes that are not valid JSON:

• <!-- → <\!-- ← \! is not a legal JSON escape
• --> → --\> ← \> is not a legal JSON escape

Any page whose props contained a literal --> (very common in docs that quote shell output, code examples, or arrow markers) would fail at hydration with:

[Pyxle] Failed to parse initial props
SyntaxError: Bad escaped character in JSON

The fix swaps the problematic replacements for Unicode escapes — which are valid JSON — and still neutralise the HTML-tokenizer sequences:

• <!-- → \u003c!--
• --> → --\u003e

🧪 Tests

• Added a parametrised test_output_is_valid_json_after_escape that round-trips escaped output through json.loads to catch this class of regression.
• 1127 total tests, all passing.

📦 Install

pip install --upgrade pyxle-framework==0.2.3

🙏 Migration

None. This is a pure bug fix — existing apps just need to redeploy with 0.2.3 to get correct behaviour.