We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am transferring a site from Jekyll to 11ty. There I was hoping that where filter is working in the same way.
I can get the baked in where filter to work with strings. However, it does not work if the key contains an array.
where
If my frontmatter has this:
tags: - Liquidjs
Then I cannot do:
{% assign site_posts = collections.posts | where: "tags", "Liquidjs" %}
It will work, if tags were just a string:
tags: Liquidjs
Making it compatible with Jekyll liquid where filter, would make transitions way easier.
The text was updated successfully, but these errors were encountered:
feat: support Jekyll style where, #768
8064384
9107eb1
chore(release): 10.19.0 [skip ci]
062b351
# [10.19.0](v10.18.0...v10.19.0) (2024-11-17) ### Features * allow drops in property access ([#769](#769)) ([11f013b](11f013b)) * support Jekyll style `where`, [#768](#768) ([9107eb1](9107eb1))
I found Jekyll where is indeed different from that of Shopify/liquid. Added a jekyllWhere option to mimic Jekyll behaviour, please try 10.19.0.
jekyllWhere
10.19.0
Sorry, something went wrong.
No branches or pull requests
I am transferring a site from Jekyll to 11ty. There I was hoping that where filter is working in the same way.
I can get the baked in
where
filter to work with strings. However, it does not work if the key contains an array.If my frontmatter has this:
Then I cannot do:
{% assign site_posts = collections.posts | where: "tags", "Liquidjs" %}
It will work, if tags were just a string:
tags: Liquidjs
Making it compatible with Jekyll liquid where filter, would make transitions way easier.
The text was updated successfully, but these errors were encountered: