Case insensitive keys in YAML-style Meta-Data about mkdocs HOT 4 CLOSED

Could you elaborate why you want this feature?

from mkdocs.

In this case I was using uppercase keys and was wrongly assuming case did not matter.

I think it is safe to generally assume that YAML keys are case-sensitive, since YAML itself is case-sensitive.

Since I already have a lot of documents with uppercase keys

Do you mean that you have a lot of Markdown pages with front-matter metadata using uppercase keys, to configure for example plugins or your own metadata? Then you'd like to use uppercase for MkDocs own metadata, for consistency's sake?

IMO it is not worth it, and case-insensitivity does not play well with other tools anyway, such as JSON schemas describing possible keys and values. This could also make things confusing: if keys are case-insensitive in front-matter, are they too in mkdocs.yml? if no, why not? etc.

from mkdocs.

Sure, the requirement that all keys are case sensitive and mkdocs expects them to be lowercase, was surprising behavior for me and I only found out about it after specifically searching for case sensitivity in the docs when things did not work for me as expected. In this case I was using uppercase keys and was wrongly assuming case did not matter.

Since I already have a lot of documents with uppercase keys, I was looking for an configuration option to change the default.

I'm not suggesting that the current default is wrong, I'm just wondering if one could add an config option to make the keys case-insensitive.

from mkdocs.

Hm sorry, that's not a convincing use case. Even you will be better off by globally replacing the existing keys with a consistent style of keys rather than enabling a case-insensitive mode if it existed.

from mkdocs.