Skip to content

Docs: Fix template_exclusion_filter explanation #150

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rafaelfranca merged 1 commit into from
Sep 18, 2025
Merged

Docs: Fix template_exclusion_filter explanation #150

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ Available configuration options are:
by `SafeErbTester` when determining whether or not a given attribute value will be eval'ed as javascript.
Defaults to `[/\Aon/i]` (matches `onclick` for example).
* `template_exclusion_filter`: This is called when determining whether to apply runtime checks on a `.erb` template.
When this `Proc` returns false, no safety checks are applied and parsing is done using the default Rails erubi engine.
When this `Proc` returns true, no safety checks are applied and parsing is done using the default Rails erubi engine.
For example, to exclude erb templates provided by libraries, use: `Proc.new { |filename| !filename.start_with?(Rails.root.to_s) }`.
Defaults to `nil` (all html.erb templates are parsed).

Expand Down
Loading