[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 摘要。