aboutsummaryrefslogtreecommitdiffstats
path: root/actionpack/test/template/erb
Commit message (Collapse)AuthorAgeFilesLines
* Remove unnecessary in HTML 5 type attribute with default valueAndrey A.I. Sitnik2012-04-051-3/+3
|
* Revert "Remove deprecated form_for with strings or symbols"José Valim2010-11-182-5/+2
| | | | | | | | | | | | | | | | This code was not deprecated. What was deprecated is the following: form_for(:foo, @foo) Which now should be rewritten as: form_for(@foo, :as => :foo) The following format is valid: form_for(:foo) This reverts commit be797750e6ce866ea08307f63bf35304a965c8d4.
* Remove deprecated form_for with strings or symbolsLeonardo Capillera2010-11-182-2/+5
| | | | Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
* Remove duplicate helper methodKrekoten' Marjan2010-09-251-3/+0
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Remove deprecated support to <% form_for %> and several ↵José Valim2010-08-291-34/+10
| | | | ActionController::Base methods.
* Fix several known web encoding issues:wycats2010-06-272-3/+3
| | | | | | | | | | | | | | | | | | | | | | | * Specify accept-charset on all forms. All recent browsers, as well as IE5+, will use the encoding specified for form parameters * Unfortunately, IE5+ will not look at accept-charset unless at least one character in the form's values is not in the page's charset. Since the user can override the default charset (which Rails sets to UTF-8), we provide a hidden input containing a unicode character, forcing IE to look at the accept-charset. * Now that the vast majority of web input is UTF-8, we set the inbound parameters to UTF-8. This will eliminate many cases of incompatible encodings between ASCII-8BIT and UTF-8. * You can safely ignore params[:_snowman_] TODO: * Validate inbound text to confirm it is UTF-8 * Combine the whole_form implementations in form_helper_test and form_tag_helper_test
* changed from :object_name to :as on form_for apiSantiago Pastorino2010-04-051-1/+1
|
* Refactored url_for in AV to have its own instances of the helpers instead of ↵wycats2010-04-031-9/+2
| | | | proxying back to the controller. This potentially allows for more standalone usage of AV. It also kicked up a lot of dust in the tests, which were mocking out controllers to get this behavior. By moving it to the view, it made a lot of the tests more standalone (a win)
* Modify assert_template to use notifications. Also, remove ↵Carlhuda2010-03-173-37/+44
| | | | ActionController::Base#template since it is no longer needed.
* Add deprecation notices for <% %>.Carlhuda2010-03-151-6/+18
| | | | | | | | | | | | | | | | * The approach is to compile <% %> into a method call that checks whether the value returned from a block is a String. If it is, it concats to the buffer and prints a deprecation warning. * <%= %> uses exactly the same logic to compile the template, which first checks to see whether it's compiling a block. * This should have no impact on other uses of block in templates. For instance, in <% [1,2,3].each do |i| %><%= i %><% end %>, the call to each returns an Array, not a String, so the result is not concatenated * In two cases (#capture and #cache), a String can be returned that should *never* be concatenated. We have temporarily created a String subclass called NonConcattingString which behaves (and is serialized) identically to String, but is not concatenated by the code that handles deprecated <% %> block helpers. Once we remove support for <% %> block helpers, we can remove NonConcattingString.
* %= works for content_tag and does not require parenthesis on method callJosé Valim2010-03-121-2/+2
|
* Make form helpers work with <%= wycats2010-03-091-12/+34
|
* Deprecate block_called_from_erb? pending a solution for getting it into appsCarlhuda2010-03-091-0/+60