Where filter always treats value as a string

[omgmog]

I noticed recently that the where: filter treats the value option as a string, even if a boolean is used:

Example post frontmatter:

---
title: foo
featured: true

---

Example usage of where: filter:

{% assign featured_posts = ( site.posts | where: "featured", true ) %}

>> featured_posts is empty

The same result is seen if we wrap true in quotes on the where: filter:

{% assign featured_posts = ( site.posts | where: "featured", "true" ) %}

>> featured_posts is empty

To make this work I had to wrap the true in quotes in both cases:

---
title: foo
featured: "true"

---

{% assign featured_posts = ( site.posts | where: "featured", "true" ) %}

>> featured_posts contains foo

[parkr]

yeah, the input to that where filter is always a string. We should do a .to_s when looking at the value to check against

[pathawks]

This would be really useful in, for example, jekyll-sitemap, where we currently need an additional conditional in every loop. Being able to use the where filter would be much nicer, I think.

[omgmog]

👏