Remove encode_special_chars option from strip_tags#28061
Remove encode_special_chars option from strip_tags#28061rafaelfranca merged 1 commit intorails:masterfrom andrewhood125:strip_tags_update
encode_special_chars option from strip_tags#28061Conversation
|
Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @rafaelfranca (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. This repository is being automatically checked for code quality issues using Code Climate. You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a Pull Request is considered ready to review. Please see the contribution instructions for more information. |
|
|
|
@Erol I added some docs and examples regarding the behavior let me know what you think and if there is anywhere docs should be updated. |
|
Updated with master and resolved conflicts in |
rafaelfranca
left a comment
There was a problem hiding this comment.
Seems good to me. Could you squash your commits?
|
Squashed. 👍 |
Since rails#28061, the output of `strip_tags` encodes HTML entities like `&`, and should thus be considered "html safe". The result should be printed without further escaping, else double-encoding will occur.
This pr removes the misnomer option
encode_special_chars: falsefrom thestrip_tagshelper.Fixes: #28060