|
1 | 1 | # remark-notro |
2 | 2 |
|
| 3 | +## 0.0.9 |
| 4 | + |
| 5 | +### Patch Changes |
| 6 | + |
| 7 | +- [#155](https://github.com/mosugi/notro/pull/155) [`2c67a6d`](https://github.com/mosugi/notro/commit/2c67a6da5d406e42e4259a6be13baf3606eb1ef7) Thanks [@mosugi](https://github.com/mosugi)! - Fix: Notion block boundaries now render as separate paragraphs |
| 8 | + |
| 9 | + **Fix 13 (revised): Block boundary expansion (`\n` → `\n\n`)** |
| 10 | + Notion's Markdown API outputs each block (paragraph, heading, etc.) separated by a |
| 11 | + single `\n`. CommonMark treats a lone `\n` between text lines as a soft break, |
| 12 | + collapsing all consecutive blocks into one `<p>`. This fix expands every single `\n` |
| 13 | + between non-blank lines to `\n\n` so remark produces separate block-level elements, |
| 14 | + matching Notion's intended structure. Fenced code blocks and directive blocks (`:::`) |
| 15 | + are excluded from the expansion. `<br>` (intra-block Shift+Enter) is normalized to |
| 16 | + `<br/>` for correct rehype-raw handling. |
| 17 | + |
| 18 | +- [#153](https://github.com/mosugi/notro/pull/153) [`f26a4c4`](https://github.com/mosugi/notro/commit/f26a4c4c836c742dc2bc7e33d80c7bf39035c18d) Thanks [@mosugi](https://github.com/mosugi)! - Fix: bold markers and line breaks now render correctly in Notion content |
| 19 | + |
| 20 | + **Fix 13: `<br>` normalized to `<br/>`** |
| 21 | + Notion's Markdown API uses `<br>` (without slash) for inline line breaks |
| 22 | + (e.g. `月曜日<br>10:00~18:00`). Normalized to self-closing `<br/>` for |
| 23 | + correct inline rendering by rehype-raw. |
| 24 | + |
| 25 | + **Fix 15: `**bold**`converted to`<strong>bold</strong>` in pre-processing** |
| 26 | + CommonMark delimiter run rules silently break `**bold**` rendering when `**` |
| 27 | + is adjacent to CJK close punctuation (e.g. `**『曜日時間固定』**` fails |
| 28 | + because `』` is Unicode category Pf). The Notion API also sometimes outputs |
| 29 | + trailing spaces before the closing `**` (e.g. `**text **`). Pre-converting |
| 30 | + bold markers to `<strong>` tags bypasses both issues. Code spans and fenced |
| 31 | + code blocks are excluded from the conversion. |
| 32 | + |
| 33 | +- [#153](https://github.com/mosugi/notro/pull/153) [`f26a4c4`](https://github.com/mosugi/notro/commit/f26a4c4c836c742dc2bc7e33d80c7bf39035c18d) Thanks [@mosugi](https://github.com/mosugi)! - Fix: colon in time formats (10:00, 18:30) no longer produces spurious `<div></div>` elements |
| 34 | + |
| 35 | + `micromark-extension-directive` treats `:` (char code 58) as the trigger for |
| 36 | + inline text directives, so time formats like `10:00` were parsed as an inline |
| 37 | + directive named `00` (or `30` etc.), emitting an empty `<div>` element after the |
| 38 | + digit before the colon. |
| 39 | + |
| 40 | + The fix restricts the directive micromark extension to flow-level constructs |
| 41 | + (container `:::callout` and leaf `::callout`) only, by removing the `text` |
| 42 | + property from the extension object before registering it. Notion content never |
| 43 | + uses inline text directives (`:name[...]`), so this change is safe and has no |
| 44 | + functional impact on Notion rendering. |
| 45 | + |
3 | 46 | ## 0.0.8 |
4 | 47 |
|
5 | 48 | ### Patch Changes |
|
0 commit comments