Skip to content

[5.x] More Antlers defaults#14125

Merged
jasonvarga merged 4 commits into5.xfrom
more-defaults
Mar 2, 2026
Merged

[5.x] More Antlers defaults#14125
jasonvarga merged 4 commits into5.xfrom
more-defaults

Conversation

@jasonvarga
Copy link
Member

This builds on #14092 and does the following:

  • Tags and modifiers within the App namespace (i.e. your own tags/modifiers) are automatically allowed. Any knowledge of your own code would be internal and presumably safe.
  • Adds a bunch more safe core modifiers to the defaults.

@jasonvarga jasonvarga merged commit 1395a5e into 5.x Mar 2, 2026
26 checks passed
@jasonvarga jasonvarga deleted the more-defaults branch March 2, 2026 18:26
@daun
Copy link
Contributor

daun commented Mar 3, 2026

@jasonvarga This only applies to Antlers in content fields, right? Meaning templates/views would still allow any modifiers including those from the vendor folder? Just making sure since we tend to package our common modifiers and use them from a composer package.

@jasonvarga
Copy link
Member Author

Yes. In actual templates you can continue to do whatever you want.

@efc
Copy link
Contributor

efc commented Mar 5, 2026

Where can we find a list of the "safe core" modifiers and tags?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants