I’m trying to build a Hugo site referencing Characters and Novels of a very famous series of french books. Each characters is in different novels. The pairing is made by ids (from a previous framework) So in my novel front matter: --- title: La Fortune des Rougon id: 75928 date: …

Found the workaround… {{ range .Params.rm_novel_characters }} {{ $.Scratch.Add "chars" (slice (int .))}} {{ end }} and then {{ range where .Site.Pages "Params.id" "in" ($.Scratch.Get "chars") }} Now I am wondering if the range where should not be agnostic of type, considering yaml and toml l…

I have also noticed that . Oddly all Page params get casted as strings. To add to that, the except same params when used as resources params , do not get string-casted.

(Moved my question to a separate post .)

Interesting. Front Matter is great but yaml and toml not forcing the use of quotes to define strings makes it hard to guess right the type of the value intened by the editor. I don’t know if there is a confusion proof way to go :confused:

[image] regis: yaml and toml not forcing the use of quotes to define strings makes it hard to guess right the type of the value intened by the editor. But it seemed to have done the correct “guessing” for resources.params. I am just curious why forced string casting is done for Page params.

Me too, I suggest you open a new discussion about just that. Will be easier to spot for everyone involved I suppose.

[image] regis: I suggest you open a new discussion about just that Done .

Range where .Params.id "in" : integer vs strings

support

kaushalmodi January 23, 2018, 7:36pm 8

Done.

Topic		Replies	Views
Range Params within markdown! support	4	376	July 2, 2021
[solved] Pagination: problem with selecting multiple page types support pagination	6	1793	October 11, 2019
How to Range 2 Different (front matter) Params in the same time support	6	559	August 30, 2018
Filtering pages with the in operator fails support	7	717	November 24, 2025
Number comparison in WHERE clause support	1	959	January 21, 2018

Range where .Params.id "in" : integer vs strings

Related topics