Config Params should be all lowercase or not?

stephenpiscura · June 14, 2019, 3:02am

I see that this issue is marked as closed:

github.com/gohugoio/hugo

Inconsistent Handling of .Param Case Sensitivity

opened 05:17PM - 13 Aug 18 UTC

closed 03:54PM - 14 Aug 18 UTC

marcojakob

Bug Outdated

There is an inconsistency in how Hugo handles capitalized `.Params`. Consider… the following front matter parameter: ``` +++ sidebarName = "Introduction" +++ ``` The name `sidebarName` is handled differently in various cases: ``` {{ .Params.sidebarName }} // This works! {{ .CurrentSection.Params.sidebarName }} // This does not work! ``` See also discussion here: https://discourse.gohugo.io/t/config-params-should-be-all-lowercase-or-not/5051/ As [@bep wrote](https://discourse.gohugo.io/t/config-params-should-be-all-lowercase-or-not/5051/2): > All config keys are stored as lower-case to be able to access them with any case. But it seems if we access them via a `section` (or maybe other ways?), then this is not true. --- Hugo version: `v0.46/extended windows/amd64`

But i just ran into it again, and outlined my experience here:

I was banging my head against the wall until someone suggested changing my custom parameter from camelCase to all lower case.

Is it ‘officially’ advised that custom params be written only in lower case?

Topic		Replies	Views
Config and Frontmatter params case-inconsistency support	2	890	June 27, 2019
Case sensitivity: index function supports only all-lower-case key values support	1	705	October 14, 2017
Would be great if frontmatter variables didn't have to be all lowercased feature	9	3045	November 27, 2015
Aren't all front-matter parameters lower-cased internally? support	4	1052	March 15, 2018
Config no longer case insensitive? support	3	1246	October 3, 2014

Config Params should be all lowercase or not?

Related topics