Cosmin Popovici

Forgot about multiple filters, so this needs to be taken into account. For example: ``` {{ "foo\nbar" | striptags(true) | escape | nl2br }} ``` I think the `` tag...

Yep, I get someone could do that, but you wouldn't have to if we have both `{{ var | filterName }}` and the `` tag. You use the inline one...

> i think , `` can have more control over the HTML I guess. (not sure though) I think both are useful, as there are situations where you can't use...

My feedback: 1. If we go for the first one (multiple filters split by `|`), the second one would also be possible. I think it would be awesome to be...

Same as your other examples: ``` ``` Where `'default'` can be an empty string `''` in order to output ``.

I'm ok with `set`, too 👍 `posthtml-modules` - since it accepts plugins, you can call it and pass `posthtml-expressions` as a plugin (with `initial: true`). Already [doing it for components...

I should mention that you can currently trick it into not outputting `undefined` by using an HTML comment: ```html Title is {{ title }} ``` That will output `Title is...

`{{ page?.title ?? 'Scrum' }}` - optional chaining is only available starting with Node 14. Honestly I don't really care if we can use `set`, `const`, or simply `{{ foo...

`computed` is actually cool and might come in handy! However, this is about being able to do that right in the template - the user might not have access to...

All loop tests pass and that works fine, can you please share a repository that reproduces the issue?