Improvement: add EXTRA_MARKDOWN_EXTENSIONS to avoid overriding the defaults #11

New Issue

bss · 2021-05-07T00:10:07-05:00

bss commented

2021-05-07 00:10:07 -05:00

No description provided.

bss commented

2021-06-07 11:26:47 -05:00

Rethinking this and maybe I'm going to close this, the site already ships with specifically specifying the one extension it needs (meta), and the rest of the extensions are all optional and (theoretically) a site-specific choice, so... maybe overriding MARKDOWN_EXTENSIONS is correct.

IOW, why have MARKDOWN_EXTENSIONS and EXTRA_MARKDOWN_EXTENSIONS if both are configurable options, and the only reason I think I need the latter is I'm me, wanting to add an extension to the shipped config.py and update all my sites, rather than adding it to each site's instance/config.py?

Rethinking this and maybe I'm going to close this, the site already ships with specifically specifying the one extension it needs (meta), and the rest of the extensions are all optional and (theoretically) a site-specific choice, so... maybe overriding `MARKDOWN_EXTENSIONS` is correct. IOW, why have `MARKDOWN_EXTENSIONS` and `EXTRA_MARKDOWN_EXTENSIONS` if both are configurable options, and the only reason I think I need the latter is I'm me, wanting to add an extension to the shipped `config.py` and update all my sites, rather than adding it to each site's `instance/config.py`?

bss closed this issue

2021-06-24 15:13:51 -05:00

Sign in to join this conversation.