New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does mike work with new INHERIT
mkdocs config feature?
#59
Comments
Looking at the MkDocs docs, the short answer is "no". If you want to use I'm a little skeptical about the |
Good and clear answer, thank you. I hadn't considered the consequences, only the inflexibility, such was my desperation to try anything to tame multiple |
I'm going to reopen this to track the fix for |
fyi - I've managed to get some success for both inherit and for !ENV by leveraging mkdocs.utils.yaml_load instead of yaml.load in mkdocs_utils.py within a fork. These two lines (plus one for the import) are the only things I needed to change, but it's entirely possible I've just not hit a use case that doesn't work for yet. |
@chris-twiner Looking at the implementation of |
Ok, |
Very cool, many thanks! |
Any ETA for 1.1.0? |
Probably this week, since the only remaining thing I want to add is some documentation about working with CI (that's a pretty common issue that gets filed). |
Ok, I've just published v1.1.0, so now this should be available to everyone via PyPI. |
It's excellent and pushed to production! Thanks. |
Is mike 1.0.1 compatible with mkdocs 1.2
INHERIT
token?I'm rejigging a set of configs to use the
INHERIT
feature but when running mike I geterror: 'dict' object has no attribute 'insert'
.The text was updated successfully, but these errors were encountered: