You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want all the extensions in extra, so instead of requesting all of them individually I just do something like
html = markdown.markdown(text, extensions=['extra'])
But I need to specify some options (for the 'footnotes' extension), so I include those in the options dict. These options get ignored when just specifying 'extra', I have to explicitly add 'footnotes' to the extensions list for them to be used.
I thought this was documented but I'm not finding it. The extra extension is just a wrapper which enables each of the individual extensions. However, extra only has access to config options for the extra key. Therefore, for extra to have access to the configs to pass them on to the individual extensions, you need to nest the individual extensions within the extra config. Like this:
I want all the extensions in extra, so instead of requesting all of them individually I just do something like
But I need to specify some options (for the 'footnotes' extension), so I include those in the options dict. These options get ignored when just specifying 'extra', I have to explicitly add 'footnotes' to the extensions list for them to be used.
A simple test case:
python-markdown will re-use the footnote numbering, even though I set UNIQUE_IDS.
The text was updated successfully, but these errors were encountered: