1. 11 5月, 2011 1 次提交
  2. 01 5月, 2011 1 次提交
  3. 26 4月, 2011 1 次提交
  4. 05 3月, 2011 1 次提交
  5. 04 3月, 2011 1 次提交
  6. 05 12月, 2010 3 次提交
  7. 10 10月, 2010 1 次提交
  8. 14 8月, 2010 2 次提交
  9. 17 6月, 2010 1 次提交
  10. 11 6月, 2010 1 次提交
  11. 25 5月, 2010 4 次提交
  12. 02 5月, 2010 1 次提交
  13. 14 4月, 2010 1 次提交
  14. 17 3月, 2010 2 次提交
  15. 16 3月, 2010 1 次提交
  16. 26 2月, 2010 1 次提交
  17. 19 2月, 2010 2 次提交
  18. 01 2月, 2010 1 次提交
    • Y
      For performance reasons, you can no longer call html_safe! on Strings.... · 4cbb9db0
      Yehuda Katz 提交于
      For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).
      
        * Additionally, instead of doing concat("</form>".html_safe), you can do
          safe_concat("</form>"), which will skip both the flag set, and the flag
          check.
        * For the first pass, I converted virtually all #html_safe!s to #html_safe,
          and the tests pass. A further optimization would be to try to use
          #safe_concat as much as possible, reducing the performance impact if
          we know up front that a String is safe.
      4cbb9db0
  19. 27 1月, 2010 1 次提交
  20. 25 12月, 2009 1 次提交
  21. 10 11月, 2009 1 次提交
  22. 10 2月, 2009 1 次提交
  23. 28 10月, 2008 1 次提交
  24. 25 8月, 2008 1 次提交
  25. 17 7月, 2008 1 次提交
  26. 08 7月, 2008 1 次提交
  27. 07 7月, 2008 2 次提交