1. 24 4月, 2014 8 次提交
  2. 23 4月, 2014 8 次提交
  3. 22 4月, 2014 8 次提交
  4. 21 4月, 2014 9 次提交
  5. 20 4月, 2014 7 次提交
    • A
      Merge pull request #14821 from jonatack/patch-5 · 0044bfb1
      Arthur Nogueira Neves 提交于
      Fix code indentation and improve formatting
      0044bfb1
    • A
      [ci skip] builtin -> built-in · 0c2854fa
      Akshay Vishnoi 提交于
      0c2854fa
    • J
      Fix code indentation and improve formatting · 1365af18
      Jon Atack 提交于
      in the Getting Started Guide.
      
      This PR regroups #14817, #14818 and #14819 into one commit.
      
      [skip ci]
      1365af18
    • R
      Merge pull request #14816 from jonatack/patch-2 · b1000ead
      Robin Dupret 提交于
      Grammar fix in Getting Started Guide [ci skip]
      b1000ead
    • J
      Grammar fix in Getting Started Guide · cd86201e
      Jon Atack 提交于
      cd86201e
    • A
      Make URL escaping more consistent · 5460591f
      Andrew White 提交于
      1. Escape '%' characters in URLs - only unescaped data
         should be passed to URL helpers
      
      2. Add an `escape_segment` helper to `Router::Utils`
         that escapes '/' characters
      
      3. Use `escape_segment` rather than `escape_fragment`
         in optimized URL generation
      
      4. Use `escape_segment` rather than `escape_path`
         in URL generation
      
      For point 4 there are two exceptions. Firstly, when a route uses wildcard
      segments (e.g. *foo) then we use `escape_path` as the value may contain '/'
      characters. This means that wildcard routes can't be optimized. Secondly,
      if a `:controller` segment is used in the path then this uses `escape_path`
      as the controller may be namespaced.
      
      Fixes #14629, #14636 and #14070.
      5460591f
    • A
      Optimize URI escaping · a6179257
      Andrew White 提交于
      The URI::Parser#escape method is a general use method that has to deal
      with a variety of input however our use of it is limited in scope so
      we can increase the performance by implementing our specific needs
      within ActionDispatch::Journey::Router::Utils directly.
      
      If there is no encoding required then there is no change in performance
      or number of objects allocated, but for each character that needs to be
      encoded we save five object allocations and gain a performance boost.
      The performance boost seen varies from 20% when there is one character
      to over 50% when encoding ten characters.
      a6179257