It seems to me that setting some values for the override (aka the conf.py file) don't override theme set options. Example:
[tool.mudkip]
preset = "furo"
title = "my-epic-docs"
[tool.mudkip.override]
...
pygments_style = "material"
Here, I wish to change the code highlighting style for pygments to material as furo uses a different theme. Removing preset = "furo" enables for my code highlighting theme to work while enabling furo causes my option to effectively get ignored. It seems to me that my overrides get set first, and then the furo preset gets set, but I can't be too certain.
Edit: furo has pygments_dark_style but it seems to me that mudkip isn't recognizing or letting sphinx recognize this field based on how the config is getting parsed or something.
It seems to me that setting some values for the override (aka the
conf.pyfile) don't override theme set options. Example:Here, I wish to change the code highlighting style for pygments to
materialas furo uses a different theme. Removingpreset = "furo"enables for my code highlighting theme to work while enablingfurocauses my option to effectively get ignored. It seems to me that my overrides get set first, and then the furo preset gets set, but I can't be too certain.Edit:
furohaspygments_dark_stylebut it seems to me that mudkip isn't recognizing or letting sphinx recognize this field based on how the config is getting parsed or something.