--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-co...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.
I understand the reasons why it's usually not desired for strings to be html safe by default but I don't see how useful this change is when applied to partials rendering, that's why I asked for an example. I couldn't find any real scenario where it would be desired when looking at the issues you mentioned.
I understand why we don't want every file to be interpreted by ERB by default and why RAW is a better fit, I just fail to see how not being html safe would be useful for partial rendering...
The babysitter should arrive in a few minutes and I'll try to open a PR to change the changelog anyway...
Or maybe we should automatically flag .js and .htm(l) extensions as html safe after using the raw handler, as they are common extensions expected to be used as partials...