mirror of
https://github.com/getpaseo/paseo.git
synced 2026-07-29 12:01:31 +00:00
8c6abcb41f
* fix(app): render bold/italic/strikethrough via UITextView span on iOS strong/em/s had no custom render rule and fell back to react-native-markdown-display's defaults, which wrap children in a plain RN <Text>. On iOS the paragraph/textgroup are native UITextViews (markdown-text.ios.tsx); a plain <Text> nested inside is not hoisted into a UITextViewChild, so its content rendered invisibly — bold/italic/ strikethrough silently disappeared (regression from #1153, v0.1.84). Route strong/em/s through MarkdownInheritedText -> MarkdownTextSpan, the same path text/textgroup already use, so the styled run composes as a UITextViewChild on iOS and stays visible + selectable. Web/Android use a plain <Text> for MarkdownTextSpan, so behavior there is unchanged. Fixes #1253 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(app): render hard/soft line breaks via UITextView span on iOS hardbreak/softbreak had no custom rule, so react-native-markdown-display emitted a plain RN <Text>{"\n"}. Inside the paragraph UITextView that plain <Text> is dropped (same root cause as strong/em/s/link): on iOS hard line breaks vanished, and a softbreak between words joined them ("one\ntwo" -> "onetwo") — the "adjacent words dropped" symptom from the original report. Route both through MarkdownTextSpan so the newline composes as a UITextViewChild on iOS; web/Android keep the same "\n". Refs #1253 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Geoffrey <geoffrey.marc@consulting-for.edenred.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>