-
-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
group_by_exp
fails with object as input
#785
Comments
I guess the issue is about tag[1].size Do we know the structure of tag here? |
|
## [10.20.1](v10.20.0...v10.20.1) (2025-01-04) ### Bug Fixes * break/continue stops whole template, [#783](#783) ([5f1a4cf](5f1a4cf)) * enumerate plain objects in where/where_exp, [#785](#785) ([#788](#788)) ([25ef104](25ef104)) * preserveTimezones support for RFC2822 date, [#784](#784) ([59cf3c0](59cf3c0))
Please try liquidjs/test/e2e/issues.spec.ts Lines 534 to 560 in 25ef104
|
It seems to be working in In In |
In Jekyll, it is possible to do
However, in liquidjs,
collections.postsByTag | group_by_exp: 'tag', 'tag[1].size'
(wherecollections.postsByTag
in Eleventy is in the same format assite.tags
in Jekyll) just ends up being[ { name: undefined, items: [ [Object] ] } ]
Running
collections.postsByTag
throughObject.entries
makes this filter work properly.This came up while migrating from Jekyll to Eleventy, but I will probably end up reimplementing this functionality, so I might not need it in the end, but I am reporting this missing functionality here.
The text was updated successfully, but these errors were encountered: