Content adapters: make params (dict) into content

support
1

Halfway into converting one of my data sources using the new Content adapters | Hugo. I created a bunch of Params (based on fields in a remote JSON file) in the _content.gotmpl file and I would like to show those param fields as content in the single layout. How can this be achieved? Thanks in advance

2

I don’t understand the question. If the map you pass into AddPage includes a params map, the params are available in a template with {{ .Params.foo }}. The example in the docs has… an example of that.

3

I was looking for a way to extract them into content instead of repeating them again. something like

<ul>
{{ range $k, $v := $params }}
  <li>{{ $k }}: {{ $v }}</li>
{{ end }}
4

Why can’t you do that?

5

Might have been a Hugo cache issue. Anything with trim foo " " was not working for the project until I restarted the server. Strange!

6

That makes no sense.

7

This worked

<ul>
{{ range $k, $v := .Params }}
  <li>{{ $k }}: {{ $v }}</li>
{{ end }}
8

Might as well ask here. Hugo is lowercasing the $k value. How to prevent that?

9

You can’t. Keys are converted to lower case internally. If it’s something simple pass through strings.FirstUpper.

10

I am now just understanding that these keys are the .Params themselves. Gotta be careful with how they are defined.

Some keys are defined with an underscore `Foo_Bar".

EDIT: This works <li>{{- $k | replaceRE "_" " " | title }}: {{ $v }}</li>

11

strings.Replace?

12

replaceRE worked! Can the keys also appear in the order they are defined in the Params? They appear alphabetically on the front end.

13

No. Unlike slices, maps are not ordered. But when you range through the map it is alphabetized by key.

14

No problem! I can live with that. I hard hard corded the keys in the previous implementation.

15

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.