-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
escape_once filter is broken #283
Comments
I don't think this ever worked in the first place o_O |
@fw42 What kind of escape, URI or CGI? |
See the code. It's using ActionView::Helpers::TagHelper.escape_once under the hood. |
In case it helps, I thought I'd point out that there's some more discussion on this in #110. |
Yeah the thing with the current implementation is that even IF the dependencies are loaded, it doesn't work. |
Fixed in #287 |
Are there plans to include this in a |
@aprescott: Not really. The 2.x branches are not being worked on anymore. |
@fw42 in that case is the 3.x branch going to see a release any time soon? It'd be great to have this fix included. |
@aprescott: We don't have a date set or anything. We are working on some refactorings (mostly for performance improvements and just general code quality) that we would like to see included. |
@fw42 👍 thanks, just curious, it'd be great to get this fix available. :) |
The escape_once filter is passing tests, but is broken in templates.
I assume that this is because the filters are set up in a different way in the tests than they are in strainer (and then in the real-thing, "ActionView::Helpers::TagHelper" raises a NameError). The whole NameError thing is super ugly. I would rather not define the filter at all if it's not available rather than returning the unescaped input.
@gauravmc, wanna take a look?
The text was updated successfully, but these errors were encountered: