Since #451 from Markdown 3.7.0, the jekyllDataString (renderer) prototype has been deprecated in favor of the jekyllDataTypographicString alias. While the jekyllDataString (renderer) prototype is still produced by globbing, we no longer allow users to set it directly by an error in #451. Therefore, setting jekyllDataString (renderer) prototype or any glob that includes jekyllDataString will produce an endless loop, since any (renderer) prototype that cannot be set is considered a glob and will be expanded ad infinitum.
Tasks
[x] Allow renderer (prototype) jekyllDataString to be set.
[x] Do not provide default jekyllDataString renderer (prototype).
[x] Test that jekyllDataString renderer (prototype) can be set.
Since #451 from Markdown 3.7.0, the
jekyllDataString
(renderer) prototype has been deprecated in favor of thejekyllDataTypographicString
alias. While thejekyllDataString
(renderer) prototype is still produced by globbing, we no longer allow users to set it directly by an error in #451. Therefore, settingjekyllDataString
(renderer) prototype or any glob that includesjekyllDataString
will produce an endless loop, since any (renderer) prototype that cannot be set is considered a glob and will be expanded ad infinitum.Tasks
jekyllDataString
to be set.jekyllDataString
renderer (prototype).jekyllDataString
renderer (prototype) can be set.CHANGES.md