Jason Varga

> Let me know what you think. If you were waiting for some approval before continuing, here it is! I have no problem with these sorts of modifiers being added....

I guess you can get the bard html by doing ```antlers {{ bard_field | where:type:text | pluck:text | join('') }} ``` It would be nice to do `{{ bard_field |...

> So at the moment that isn't possible Then I guess yeah we'll need an argument. I'd say it should _not_ use Antlers by default and then you opt into...

Antlers modifier is a good idea. I guess you can revert your changes and just assume that'll be there. #6489

Sorry, somehow I overlooked this part of your comment the other day: > Is there then an argument for renaming `bard_words` back to `bard_text`? `bard_html` gives you HTML, `bard_text` gives...

> Interface is only valid when implemented by types Is this in the spec? Where?

Sorry I'm not familiar with this package or typescript but that sounds good to me.

Can this be merged?

I came across this repo/issue looking for a partial circle solution. +1

Are there any sort of caches available to the action? (Sorry, don't really know much about Action internals yet) Perhaps a flag can be stored along with the workflow ID...