Skip to content

refactor(markdown-toolkit): rename Rendering to MarkdownInternals - #196

Merged
Jason3S merged 1 commit into
mainfrom
claude/md-markdown-internals
Nov 11, 2026
Merged

Jason3S merged 1 commit into
mainfrom
claude/md-markdown-internals

Conversation

@Jason3S

@Jason3S Jason3S commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

Summary

The internal Rendering type is now MarkdownInternals, and the names that came from it follow. The type holds the non-public side of an element, its syntax tree and its style, and nothing in it has been rendered. No behavior changes.

Changes

Names. Each took its name from the type:

Before After
Rendering MarkdownInternals
renderingKey markdownInternalsKey
renderingOf(value) markdownInternalsOf(value)
rendering (local variable) markdownInternals

Comments. The key's and the function's comments say "internals" where they said "rendering". The type gets a one-line comment, since its name doesn't say whose internals they are.

Guide example. docs/writing-comments.md quotes the function's comment as an example, so the quote is updated to match.

Not changed. The symbol's registry string and the function's signature stay as they are. This is a rename only.

The type holds the non-public side of an element: its syntax tree and
the style to write it out with. Nothing in it has been rendered, so
"Rendering" named the wrong thing, and the key, the function and the
local variables all took that name from it.

The type is now `MarkdownInternals`, and the rest follow:
`markdownInternalsKey`, `markdownInternalsOf` and `markdownInternals`.
No behavior changes.
@Jason3S
Jason3S merged commit b61657a into main Nov 11, 2026
8 checks passed
@Jason3S
Jason3S deleted the claude/md-markdown-internals branch November 11, 2026 06:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant