Skip to content
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.

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

explore: using rgrove/sanitize as the underlying sanitizer #181

Open
flavorjones opened this issue May 8, 2024 · 0 comments
Open

explore: using rgrove/sanitize as the underlying sanitizer #181

flavorjones opened this issue May 8, 2024 · 0 comments

Comments

@flavorjones
Copy link
Member

flavorjones commented May 8, 2024

(Rails Conf 2024 hack day project)

I emailed @rgrove back in early 2023 and said:

Frankly, my long-term idea is to update rails-html-sanitizer to use sanitize instead of
Loofah. Sanitize feels like a much better fit for the problem space and the API, would allow me
to potentially deprecate loofah's sanitizers over time, and would consolidate the community around
one flexible sanitization solution. Loofah remains a half-baked solution to this problem despite
the time I've put in over the years. So, you know, throw up the stop sign if you're at all worried
about having another gem be a default Rails dependency.

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

No branches or pull requests

1 participant