[Jason3S]

Summary

Rendering template or blockTemplate could throw an error when a value came from parsed text and had formatting. Those values now work, as they already did in templateDocument and inlineTemplate.

The template's style was read after the values went in, so a value's positions in its own text were looked up in the template's text. The style now comes from the template's own text.

What failed

A value with emphasis, strong text, a list or a rule could fail, depending on which characters of the template its positions landed on. It could come from any of these:

• parse
• parseDocument
• another template

md.template('Hi {@x@}.', { x: md.parse('*a*') }).toString();
// Cannot serialize emphasis with `H` for `options.emphasis`, expected `*`, or `_`
md.template('{@x@}', { x: md.parse('- a') }).toString();
// Cannot serialize items with `{` for `options.bullet`, expected `*`, `+`, or `-`

What else changes

When those characters were valid markers, the value set the template's markers with no error. That output changes:

md.template('**t** {@x@}', { x: md.parse('*a*') }).toString();
// Before: **t** *a*
// Now: **t** _a_

Usage

md.template('Hi {@x@}.', { x: md.parse('*a*') });
// Hi _a_.
md.template('{@x@}', { x: md.parse('- a') });
// - a