- 31 5月, 2012 1 次提交
-
-
由 Sergey Nartimov 提交于
Make possible to use a block in button_to helper if button text is hard to fit into the name parameter, e.g.: <%= button_to [:make_happy, @user] do %> Make happy <strong><%= @user.name %></strong> <% end %> # => "<form method="post" action="/users/1/make_happy" class="button_to"> # <div> # <button type="submit"> # Make happy <strong>Name</strong> # </button> # </div> # </form>"
-
- 28 5月, 2012 1 次提交
-
-
由 Piotr Sarnacki 提交于
When more than one directory for helpers is provided to a controller, it should preserver the order of directories. Given 2 paths: MyController.helpers_paths = ["dir1/helpers", "dir2/helpers"] helpers from dir1 should be loaded first. Before this commit, all helpers were mixed and then sorted alphabetically, which essentially would require to rename helpers to get desired order. This is a problem especially for engines, where you would like to be able to predict accurately which engine helpers will load first. (closes #6496)
-
- 27 5月, 2012 2 次提交
-
-
由 Rafael Mendonça França 提交于
This options can be used to not escape the result by default.
-
由 Rafael Mendonça França 提交于
-
- 22 5月, 2012 2 次提交
-
-
由 Carlos Galdino 提交于
The input types added are: - input[type="month"] - input[type="week"] - input[type="datetime"] - input[type="datetime-local"]
-
由 Carlos Galdino 提交于
-
- 21 5月, 2012 3 次提交
-
-
由 Rafael Mendonça França 提交于
Action Pack in the upgrading guide. [ci skip]
-
由 Andrew White 提交于
Passing path parameters with invalid encoding is likely to trigger errors further on like `ArgumentError (invalid byte sequence in UTF-8)`. This will result in a 500 error whereas the better error to return is a 400 error which allows exception notification libraries to filter it out if they wish. Closes #4450
-
由 Andrew White 提交于
Currently Rack raises a TypeError when it encounters a malformed or ambiguous hash like `foo[]=bar&foo[4]=bar`. Rather than pass this through to the application this commit captures the exception and re-raises it using a new ActionController::BadRequest exception. The new ActionController::BadRequest exception returns a 400 error instead of the 500 error that would've been returned by the original TypeError. This allows exception notification libraries to ignore these errors if so desired. Closes #3051
-
- 20 5月, 2012 1 次提交
-
-
由 David Chelimsky 提交于
Before this change, assert_recognizes, assert_generates, and assert_routing raised ActionController::RoutingError when they failed to recognize the route. This commit changes them to raise Assertion instead. This aligns with convention for logical failures, and supports reporting tools that care about the difference between logical failures and errors e.g. the summary at the end of a test run. - Fixes #5899
-
- 19 5月, 2012 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
Make the method API more clear by explicitly showing the expected arguments. This means that the options cannot be passed as second argument because we are not relying on extract_options! anymore, you are expected to give a selected key or `nil` if you want to pass options, as it is the last argument. Notice that this does not change the current method arguments contract available in 3.2, it just brings back the same functionality with the divider addition.
-
- 18 5月, 2012 3 次提交
-
-
由 Alex Soulim 提交于
-
由 Jeremy Walker 提交于
-
由 José Valim 提交于
-
- 15 5月, 2012 3 次提交
-
-
由 José Valim 提交于
Revert "Revert "Remove `:disable_with` in favor of `'data-disable-with'` option from `submit_tag`, `button_tag` and `button_to` helpers."" Finally remove `:disable_with` but use `:data => { :disable_with => ... }` in examples to show off a better API (which looks nicer in Ruby 1.9) This reverts commit a5c38a9c.
-
由 José Valim 提交于
Revert "Remove `:disable_with` in favor of `'data-disable-with'` option from `submit_tag`, `button_tag` and `button_to` helpers." `disable_with:` is much easier to type than `"data-disable-with" =>`, and the fact it uses "data-disable-with" => is an implementation concern, it should not affect the public API. This reverts commit 683fc4db.
-
Remove `:disable_with` in favor of `'data-disable-with'` option from `submit_tag`, `button_tag` and `button_to` helpers.
-
- 14 5月, 2012 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 13 5月, 2012 2 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Angelo Capilleri 提交于
the select method (tag select) forces :include_blank if is required and no multiple and display size is one
-
- 12 5月, 2012 1 次提交
-
-
- 11 5月, 2012 1 次提交
-
-
由 Andrew White 提交于
-
- 06 5月, 2012 1 次提交
-
-
由 José Valim 提交于
-
- 03 5月, 2012 2 次提交
-
-
由 Andy Lindeman 提交于
-
由 Santiago Pastorino 提交于
-
- 30 4月, 2012 3 次提交
-
-
由 Dmitriy Kiriyenko 提交于
This replaces `include_seconds` argument with an option key `include_seconds => true` in options hash. Also `time_ago_in_words` now passes options hash, including a `locale` key, which makes in compatible with `distance_of_time_in_words`.
-
由 Rafael Mendonça França 提交于
-
由 Carlos Antonio da Silva 提交于
-
- 29 4月, 2012 3 次提交
-
-
由 Carlos Antonio da Silva 提交于
Fix failing test: Mime::JS generates "text/javascript"
-
由 Piotr Sarnacki 提交于
closes #3341
-
由 Andrew White 提交于
This may break existing tests that are asserting the whole session contents but should not break existing tests that are asserting individual keys - e.g: class SomeControllerTest < ActionController::TestCase setup do session['user_id'] = 1 end test "some test" do get :some_action, nil, { 'another_var' => 2 } # This assertion will now fail assert_equal({ 'another_var' => 2 }, session) # This assertion will still pass assert_equal 2, session['another_var] end end Fixes #1529.
-
- 16 4月, 2012 1 次提交
-
-
由 Michael de Silva 提交于
The release date details have been taken from http://weblog.rubyonrails.org/2012/3/30/ann-rails-3-2-3-has-been-released/
-
- 12 4月, 2012 1 次提交
-
-
由 Jorge Bejar 提交于
Add index method to FormBuilder. Useful when you use field_for and need to know the index number into the iteration.
-
- 30 3月, 2012 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 29 3月, 2012 2 次提交
-
-
由 Piotr Sarnacki 提交于
Changed default value for `config.action_view.embed_authenticity_token_in_remote_forms` to `false`. This change breaks remote forms that need to work also without javascript, so if you need such behavior, you can either set it to `true` or explicitly pass `:authenticity_token => true` in form options
-
由 Piotr Sarnacki 提交于
There is a regression introduced in 16ee611f, which breaks remote forms that should also work without javascript. This commit introduces config option that allows to configure this behavior defaulting to the old behavior (ie. include authenticity token in remote forms by default) Conflicts: actionpack/CHANGELOG.md
-
- 18 3月, 2012 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 15 3月, 2012 3 次提交
-
-
由 David Heinemeier Hansson 提交于
Do not include the authenticity token in forms where remote: true as ajax forms use the meta-tag value
-
由 José Valim 提交于
-
由 Santiago Pastorino 提交于
-