- 15 12月, 2015 1 次提交
-
-
由 Sam Stephenson 提交于
Introduced in e56c6354, `CacheHelper#fragment_cache_key` is a duplicate of `ActionController::Caching::Fragments#fragment_cache_key`. We now require the view to provide this method on its own (as with `view_cache_dependencies`); `ActionController::Caching::Fragments` exports its version as a `helper_method`.
-
- 22 11月, 2015 3 次提交
-
-
由 Kasper Timm Hansen 提交于
Erroneously removed in 58910dc7. The stubbing was a regression test to ensure `time_zone_select` wasn't implemented with `grep`. Rename the test and add a comment to make the intent clearer.
-
由 Kasper Timm Hansen 提交于
We never touch the index, so don't bother.
-
由 Kasper Timm Hansen 提交于
When calling `test_time_zone_select_with_priority_zones_as_regexp` it would define `=~` on the fake zones, but it would never be cleaned up because of the zone cache. Nuke it so `test_time_zone_select_with_priority_zones_as_regexp_using_grep_finds_no_zones` accidentally find any zones because of `=~` being implemented.
-
- 21 11月, 2015 1 次提交
-
-
由 Nishant Modak 提交于
-
- 13 11月, 2015 1 次提交
-
-
由 yui-knk 提交于
This commit fixes the bug convering `false` to `locals[as]` when `options[:object]` is `false` (close #22260).
-
- 11 11月, 2015 1 次提交
-
-
由 Christoph 提交于
According to the W3 spec[1] the value should use a 1-based index and not a 0-based index for the week number. [1]: http://www.w3.org/TR/html-markup/datatypes.html#form.data.week
-
- 10 11月, 2015 1 次提交
-
-
由 Christoph 提交于
According to the W3 spec[1] the value should use a 1-based index and not a 0-based index for the week number. [1]: http://www.w3.org/TR/html-markup/datatypes.html#form.data.week
-
- 08 11月, 2015 1 次提交
-
-
由 Grzegorz Witek 提交于
Now both `javascript_include_tag` and `stylesheet_tag` can accept `host` option to provide custom host for the asset
-
- 04 11月, 2015 2 次提交
-
-
由 Damien Burke 提交于
`link_to :back` creates a link to whatever was passed in via the referer header. If an attacker can alter the referer header, that would create a cross-site scripting vulnerability on every page that uses `link_to :back` This commit restricts the back URL to valid non-javascript URLs. https://github.com/rails/rails/issues/14444
-
由 Rafael Mendonça França 提交于
-
- 03 11月, 2015 1 次提交
-
-
由 Yuki Nishijima 提交于
-
- 30 10月, 2015 2 次提交
-
-
由 Paul Grayson 提交于
It used to behave like this: url_for(controller: 'x', action: 'y', q: {}) # -> "/x/y?" We previously avoided empty query strings in most cases by removing nil values, then checking whether params was empty. But as you can see above, even non-empty params can yield an empty query string. So I changed the code to just directly check whether the query string ended up empty. (To make everything more consistent, the "removing nil values" functionality should probably move to ActionPack's Hash#to_query, the place where empty hashes and arrays get removed. However, this would change a lot more behavior.)
-
由 Lecky Lao 提交于
making selected value to accept Hash like the default option. E.g. selected: {day: params[:day].to_i, month: params[:month].to_id} Adds in test test_date_select_with_selected_in_hash and change log fixes typo in CHANGELOG
-
- 29 10月, 2015 2 次提交
-
-
由 Genadi Samokovarov 提交于
Stumbled upon this one while trying to deprecate the String/Symbol passing to `form_for`. This test passed on an accident, because the signature of `form_for` currently accepts 2 positional arguments and a block. Calling it with the wrong number of arguments caused: ```ruby (byebug) form_for(:post, @post, html: { id: 'create-post' }) *** ArgumentError Exception: wrong number of arguments (3 for 1..2) ``` This made the test pass, because it was still an `ArgumentError`. :-)
-
由 Kasper Timm Hansen 提交于
It's already represented in the key name. Demonstrate with a test. Also test that the default isn't output.
-
- 21 10月, 2015 1 次提交
-
-
由 Vasiliy Ermolovich 提交于
-
- 07 10月, 2015 1 次提交
-
-
由 Jeremy Daer 提交于
Rails 4.x and earlier didn't support `Mime::Type[:FOO]`, so libraries that support multiple Rails versions would've had to feature-detect whether to use `Mime::Type[:FOO]` or `Mime::FOO`. `Mime[:foo]` has been around for ages to look up registered MIME types by symbol / extension, though, so libraries and plugins can safely switch to that without breaking backward- or forward-compatibility. Note: `Mime::ALL` isn't a real MIME type and isn't registered for lookup by type or extension, so it's not available as `Mime[:all]`. We use it internally as a wildcard for `respond_to` negotiation. If you use this internal constant, continue to reference it with `Mime::ALL`. Ref. efc6dd55
-
- 01 10月, 2015 2 次提交
-
-
由 Prakash Laxkar 提交于
-
由 Akshay Vishnoi 提交于
-
- 29 9月, 2015 1 次提交
-
-
由 Akshay Vishnoi 提交于
-
- 26 9月, 2015 1 次提交
-
-
由 Ronak Jangir 提交于
-
- 25 9月, 2015 2 次提交
-
-
由 Mauro George 提交于
as string
-
由 Mauro George 提交于
This will avoid a error be raised when the only input on the form is the `collection_radio_buttons`.
-
- 24 9月, 2015 1 次提交
-
-
由 Ronak Jangir 提交于
-
- 22 9月, 2015 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 21 9月, 2015 2 次提交
-
-
由 Akira Matsuda 提交于
-
由 Akira Matsuda 提交于
-
- 19 9月, 2015 1 次提交
-
-
由 Kir Shatrov 提交于
-
- 18 9月, 2015 2 次提交
-
-
由 Akira Matsuda 提交于
-
由 Akshay Vishnoi 提交于
Earlier when `data-disable-with` option is added direclty as in options then ```ruby submit_tag("Save", { "data-disable-with" => "Processing..." }) # => <input type="submit" name="commit" value="Save" data-disable-with="Processing..." data-disable-with="Processing..." /> ``` Now when `data-disable-with` option is added direclty as in options then ```ruby submit_tag("Save", { "data-disable-with" => "Processing..." }) # => <input type="submit" name="commit" value="Save" data-disable-with="Processing..." /> ```
-
- 06 9月, 2015 1 次提交
-
-
由 Aaron Patterson 提交于
`hfvalue` parts should always be percent encoded, so lets do that! Revert "use path escaping for email addresses" This reverts commit 21ffef38.
-
- 05 9月, 2015 2 次提交
-
-
由 Aaron Patterson 提交于
Due to e25fdad2, we are correctly using path escaping for email addresses. This commit fixes the tests to expect path escaping.
-
由 Bernerd Schaefer 提交于
The `url_for` methods in `actionpack` and `actionview` now make a copy of the provided options before generating polymorphic paths or URLs. The bug in the previous behavior is most noticeable in a case like: url_options = [:new, :post, param: 'value'] if current_page?(url_options) css_class = "active" end link_to "New Post", url_options, class: css_class
-
- 31 8月, 2015 1 次提交
-
-
由 ojab 提交于
In case of the form with nested fields_for, i. e. <%= form_for :foos, url: root_path do |f| %> <% @foos.each do |foo| %> <%= f.fields_for 'foo[]', foo do |f2| %> <%= f2.text_field :id %> <% foo.bars.each do |bar| %> <%= f2.fields_for 'bar[]', bar do |b| %> <%= b.text_field :id %> <% end %> <% end %> <% end %> <% end %> <%= f.submit %> <% end %> rails doesn't add index for 'foo' in the inner fields_for block, so field names in the outer fields_for looks like "foos[foo][#{foo_index}][id]" and in the inner "foos[foo[]][bar][#{bar_index}][id]". Submitting of such form leads to an error like: >ActionController::BadRequest (Invalid request parameters: expected Array >(got Rack::QueryParser::Params) for param `foo'): This commit adds indexes for the foos in the inner blocks, so field names become "foos[foo][#{foo_index}][bar][#{bar_index}][id]" and submitting of such form works fine as expected. Fixes #15332
-
- 28 8月, 2015 1 次提交
-
-
由 Vipul A M 提交于
- Extracted `DELIMITED_REGEX` to `delimited_regex` method and made use of user passed `options[:delimited_regex]` if available. Changed `DELIMITED_REGEX` to `DEFAULT)DELIMITED_REGEX` to signify what it means. - Added tests for number to delimited and number to currency in both actionview and activesupport. Changes Changes
-
- 27 8月, 2015 1 次提交
-
-
由 Gaurav Sharma 提交于
-
- 24 8月, 2015 1 次提交
-
-
由 Ronak Jangir 提交于
-
- 16 8月, 2015 1 次提交
-
-
由 eileencodes 提交于
Oops, I broke the build :( Fixes the method signature of `assign_parameters` which now takes 6 arguments instead of 4. We likely will end up chaning the method signature further so good to know this test is here.
-
- 12 8月, 2015 1 次提交
-
-
由 Justin Schiff 提交于
Prevents double submission by making disable_with the default. Default disable_with option will only be applied if user has not specified her/his own disable_with option, whether that is in the `data-disable-with` string form or the `:data => { :disable_with => "Saving..." }` hash form. disable_with will default to the value attribute. A configuration option was added to opt out of this functionality if the user so desires. `config.action_view.automatically_disable_submit_tag = false`
-