Forward code fence meta to renderer #7
Send to my agenttannerlinsley added labelsenhancement
tannerlinsley closed this
Sign in to join this conversation.
tannerlinsley added labelsenhancement
tannerlinsley closed this
Sign in to join this conversation.
Confirmed on 0.0.14: the parser retains the raw info-string metadata in CodeBlockNode.meta, but the high-level framework components and highlighter callback do not receive it. This is a real API gap, not a parsing failure. The lower-level AST rendering APIs and HTML extension hook can already access it.
I tested forwarding it as data-meta on pre across HTML, React SSR, and Octane SSR. The isolated candidate, including renderer simplification, still added 15 gzip bytes to the HTML entry, 4 to React, and 14 to Octane. It was not retained: the current acceptance rule is no growth against 0.0.14 in minified, gzip, or Brotli size, except for critical fixes.
Keeping this open as an enhancement. A size-neutral implementation should preserve escaping, all three renderers, raw metadata, and the absence of an attribute when metadata is missing. No new option or attribute has shipped.