[BUG]: Plain text with underscores or asterisks gets formatted as Markdown

未關閉
#127 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
半天
新手友好度
45/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
冷清
技術堆疊
dart, flutter
領域
mobile

研究方向

The payload names no files or tests, so start in the Flutter client's message rendering path and find where Markdown is parsed for sent messages. Reproduce by sending a message with an unmatched underscore and a partial Markdown opener, which the report says gets formatted. Done means unclosed or stray markers render as plain text while complete Markdown still formats correctly. The issue has no agreed expected behaviour, so confirm the intended rule with the maintainers before changing the parser.

由索引模型根據 Issue 內容生成。

描述

area: mobile bug good first issue

Context

Messages are rendered with MarkdownBody (flutter_markdown_plus). Ordinary text containing _, * or similar is sometimes treated as Markdown, e.g. snake_case_names, 2*3*4, or a lone _ at the start, so it shows up oddly formatted or with characters missing.

Steps to reproduce

  1. Send my_file_name and other_file_name.
  2. Send 2*3*4 = 24.
  3. Send _not closed.

What to do

  • Find which inputs render incorrectly (add them to a widget test).
  • Fix it, e.g. by restricting the Markdown extensions in use, requiring word boundaries for _ emphasis, or escaping unpaired markers before rendering.
  • Intentional Markdown (**bold**, _italic_, `code`) must still work.

Where to look

mobile/lib/widgets/chat_page_widgets.dart (MarkdownBody around line 228, _markdownStyle).

主要語言
Dart
星號
9
分支
5
平均合併
49 分鐘
30 天內合併 PR
34

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

CommandLineCoding/Elephant 的其他 Issue

查看 CommandLineCoding/Elephant 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。