Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

read: paragraph text that looks like a Markdown block becomes structure on publish

未关闭
#203 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
74/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
go, markdown
领域
cli

调研方向

Start in storage_to_md.go at renderBlock's block-level p case, then trace the read → publish path described in the issue. Cover the listed leading Markdown block markers, including HTML and table-like lines, and verify that escaped paragraph text remains unchanged after another read → publish cycle.

由索引模型根据 Issue 内容生成。

描述

bug

Problem

`read` and `export` write a paragraph's text as Markdown without escaping a leading block marker, so text that looks like a Markdown block turns into that block on the next publish. Found in the second review of #55.

Reproduced 2026-09-25 (read → publish):

storage read writes publish sends
`

1. not a list

`
`1. not a list` `
  1. not a list
`
`

# not heading

`
`# not heading` `

not heading

`
`

> 5 errors

`
`> 5 errors` `

5 errors

`

The page's content changes silently on a read → update cycle, and the Markdown is a fixed point after the first cycle, so no round-trip test notices. It affects every paragraph `read` writes: top level, layout cells, macro bodies, and (since #55) raw table cells. A GFM pipe-table cell is not affected, because its text is inline.

Notes

  • The fix belongs where `storage_to_md.go` renders a block-level `

    ` (`renderBlock`'s `p` case), escaping a leading marker with a backslash (`1\.`, `\#`, `\>`).

  • The markers to cover include `-`, `+`, `*`, `1.`/`1)`, `#`, `>`, a line that is only `---`/`===` (a thematic break or a setext underline), four leading spaces (indented code), and `|` if a line could read as a table row. Probably also a leading `<` that would start an HTML block.
  • The escape must survive the next read, so the Markdown stays a fixed point.
主要语言
Go
星标
2
派生
0
平均合并
2 小时 29 分钟
30 天内合并 PR
60

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

mozilla/markfluence 的其他 Issue

查看 mozilla/markfluence 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。