Koen
Here's a solution: simply downgrade to 2.3.1. The problem lies in the fact that [email protected] uses [email protected] while [email protected] uses [email protected] (those are the two versions I tested, anyway). The...
Related (i.e. can be extended to include this): https://github.com/11ty/eleventy/pull/3212
PRs have been opened: - `font`: https://github.com/ryboe/CSS3/pull/192 - `backdrop-filter`: https://github.com/ryboe/CSS3/pull/187 - `menu`: https://github.com/ryboe/CSS3/pull/186
@Luuk-van-Aggelen this issue is, I suppose, just vaguely saying "completions are not working" so there's no much of a point having two issues open that both say that. @argyleink I...
Thanks @kubiqsk, that's very helpful! It's a bit odd that it's complaining about `grey` (and not `gray`), but I recently removed the `gray()` function so this definitely looks like that...
Cool! Then I reckon the PR should fix it - let's allow @argyleink some time to review this thread and the pull request, and then we should be back to...
For what it's worth, simply changing [the `page` and `eleventy` properties](https://www.11ty.dev/docs/filters/#scoped-data-in-filters) into getters does work. Specifically, changing [these lines](https://github.com/11ty/eleventy/blob/04e07a42610f52ce367e1199f50c03ec6f79c5e8/src/Engines/Liquid.js#L61-L62) into ```js const exposedProperties = ["page", "eleventy"]; for (const property of...
It's not - that issue describes using variables inside `{% render %}`-style partials, and is not really related to filters. This bug specifically is about using filters that are _not_...
That's true, though that's out of scope for this issue, which has different semantics and accompanied by a simpler fix. Exposing the eleventy-provided globals to rendered partials may not even...
This PR has been open for a while without activity - @zachleat is this something you're interested in? I can resolve the conflicts but prefer not to do work if...