1. 04 5月, 2015 1 次提交
  2. 15 4月, 2015 1 次提交
    • J
      Fix typos and improve the documentation · 6345f31f
      Jon Atack 提交于
      This is a squash of the following commits, from first to last:
      
      -
      
      Fix minor, random things I’ve come across lately that individually
      did not seem worth making a PR for, so I saved them for one commit.
      
      One common error is using “it’s” (which is an abbreviation of “it is”)
      when the possessive “its” should be used for indicating possession.
      
      -
      
      Changes include the name of a test, so remove the `[skip ci]` (thanks @senny).
      
      -
      
      Line wrap the changes at 80 chars and add one more doc fix.
      
      -
      
      Add a missing line wrap in the Contributing to Ruby on Rails Guide.
      
      -
      
      Line wrap the `TIP` section in the Contributing to Ruby on Rails Guide as well.
      
      Rendering the guide locally with `bundle exec rake guides:generate` did
      not show any change in on-screen formatting after adding the line wrap.
      
      The HTML generated is (extra line added to illustrate where the line
      wrap takes place):
      
          <div class="info"><p>Please squash your commits into a single commit
      when appropriate. This
      
          simplifies future cherry picks and also keeps the git log
      clean.</p></div>
      
      -
      
      Squash commits.
      6345f31f
  3. 05 4月, 2015 1 次提交
  4. 13 3月, 2015 1 次提交
  5. 28 2月, 2015 1 次提交
  6. 19 2月, 2015 1 次提交
  7. 16 2月, 2015 1 次提交
  8. 04 2月, 2015 1 次提交
  9. 21 1月, 2015 1 次提交
  10. 17 1月, 2015 1 次提交
  11. 14 1月, 2015 1 次提交
  12. 24 12月, 2014 1 次提交
  13. 29 11月, 2014 1 次提交
  14. 09 10月, 2014 1 次提交
  15. 11 9月, 2014 1 次提交
  16. 09 7月, 2014 1 次提交
  17. 07 7月, 2014 1 次提交
    • R
      Update Rails versions [ci skip] · c2d96d14
      Robin Dupret 提交于
      As discussed in #15304, we need to automate this process but for now,
      having out-of-date versions is not ideal.
      
      Since master targets 4.2.0, let's also update references to the last 4.1
      version to 4.2.0.
      
      Finally, let's remove mentions to versions when this is not needed. The
      guides cover the features of the current version anyway.
      
      [Juanito Fatas + Robin Dupret]
      c2d96d14
  18. 04 6月, 2014 2 次提交
  19. 07 5月, 2014 1 次提交
    • J
      Include label value in i18n attribute lookup · d5f2c5c2
      Joshua Cody 提交于
      Previously, only the object and method name from the label tag were
      used when looking up the translation for a label. If a value is
      given for the label, this ought to be additionally used. The
      following:
      
          # form.html.erb
          <%= form_for @post do |f| %>
            <%= f.label :type, value: "long" %>
          <% end %>
      
          # en.yml
          en:
            activerecord:
              attributes:
                post/long: "Long-form Post"
      
      Used to simply return "long", but now it will return "Long-form
      Post".
      d5f2c5c2
  20. 17 4月, 2014 1 次提交
    • K
      [skip ci] Reorder i18n guide · 2c99e582
      Kyle Heironimus 提交于
      Currently, the section called "How to store your custom translations"
      has several subheadings that make no sense, such as "Translations for
      ActiveRecord models." These make more sense under the "Overview of the
      I18n API Features" section. I moved the "How to store..." section down
      to the more appropriate sub-headings "Using Different Backends" and
      "Using Different Exception Handlers" and removed the "Customize your
      i18n setup" header.
      2c99e582
  21. 16 4月, 2014 1 次提交
    • M
      [ci skip] Avoid suggesting dangerous code in i18n guide · 19b2bcc7
      Mike MacDonald 提交于
      Calling `to_sym` on user input opens apps up to Denial of Service attacks, via the symbol table being expanded to consume vast swathes of memory.
      
      It is a fairly common configuration to have DNS configured such that all subdomains route to your Rails app, in which case an attacker visits `www1.foo.com`, `www2.foo.com`, and so on until something gives.
      
      It is far less likely to have this problem with TLDs, so that change was only for consistency.
      19b2bcc7
  22. 13 4月, 2014 1 次提交
  23. 03 4月, 2014 1 次提交
  24. 13 3月, 2014 1 次提交
  25. 12 2月, 2014 1 次提交
  26. 11 2月, 2014 1 次提交
    • D
      Don't symbolize tainted data. · ec0664a6
      devlin zed 提交于
      `I18n.locale=` symbolizes its argument, so passing it `params[:locale]`
      allows one to DOS your application by visiting `...?locale=` URLS
      repeatedly, with unique values, until the never-GCed symbols monopolize
      the available memory.
      ec0664a6
  27. 04 2月, 2014 1 次提交
  28. 04 1月, 2014 1 次提交
  29. 20 12月, 2013 2 次提交
  30. 16 12月, 2013 1 次提交
  31. 28 11月, 2013 1 次提交
  32. 27 11月, 2013 1 次提交
  33. 25 11月, 2013 1 次提交
  34. 22 11月, 2013 1 次提交
  35. 13 11月, 2013 1 次提交
  36. 06 11月, 2013 1 次提交
    • D
      Clarify HTML Safe Translations [ci-skip] · 0e41b0a8
      Derek Prior 提交于
      I think it's confusing to say "Use them in views without escaping." We
      use all keys in views without escaping - the escaping is done for us
      automatically _unless_ we call html_safe or the key ends in _html.
      0e41b0a8
  37. 21 10月, 2013 1 次提交
  38. 19 10月, 2013 1 次提交