Template filters `first`/`last` counterintuitive about zola HOT 4 CLOSED

Those are built-in Tera filters. I don't think it makes sense changing the behaviour because they work on the array, they have no concept of ordering. pages | first would return the earliest if sorting by date for example but pages | reverse | first would return the latest.

Changing the meaning of first and last filter would also affect any use of the filters on other arrays, which would be even more counterintuitive imo

from zola.

pages | first would return the earliest if sorting by date

Would it? I think the array is ordered newest-first, so it would return the latest.

Changing the meaning of first and last filter would also affect any use of the filters on other arrays, which would be even more counterintuitive imo

Maybe we could order the pages array ascending (by date/order). Then pages|first would return the earliest page and pages|last the latest. We could still iterate over it in newest-first order by using the reverse filter.

from zola.

Would it? I think the array is ordered newest-first, so it would return the latest.

Yes sorry.

Maybe we could order the pages array ascending (by date/order).

I'm not sure it makes sense tbh. first and last are going to be used way less than just iterating through the pages, and in that case you want descending.
I think the current behaviour is the one that makes the most sense overall

from zola.

first and last are going to be used way less than just iterating through the pages

Yeah, maybe you're right. It would be great if the set pages = pages | reverse syntax existed in Tera. Then everyone could just use the ordering they like.

from zola.