| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
Strip nils out of default translations. Fixes #19419
|
| |
| |
| |
| |
| |
| |
| |
| | |
This logic was just doing duplicated work, since the button_to helper
relies on tag/content_tag to generate the button html, which already
handles all boolean attributes it knows about.
The code dates back to 2005: 43c470fae468ef63e0d5c3dc1e202925685fd47b.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Prevents double escaping errors, such as "&" becoming "&".
|
| | |
|
| | |
|
|\ \
| | |
| | | |
fix ActionView::Template::Error when using Streaming with capture.
|
| |/
| |
| |
| | |
can't acquire a encoding from StreamingBuffer. fixes #12001
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous version of rails(4.2.0) you can pass objects
to the default option of translation helper.
For example:
```ruby
t('foo', default: 1)
```
But on rails 4.2.1 version this kind of use stopped to work,
because started only to accept String types.
Now with this fix we can use orther value types on this
helper again.
|
| |
|
|\
| |
| | |
Merge multi_fetch_fragments.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Collections can take advantage of `multi_read` if they render one template
and their partials begin with a cache call.
The cache call must correspond to either what the collections elements are
rendered as, or match the inferred name of the partial.
So with a notifications/_notification.html.erb template like:
```ruby
<% cache notification %>
<%# ... %>
<% end %>
```
A collection would be able to use `multi_read` if rendered like:
```ruby
<%= render @notifications %>
<%= render partial: 'notifications/notification', collection: @notifications, as: :notification %>
```
|
| |
| |
| |
| |
| |
| |
| |
| | |
Makes caching a collection of template partials faster using `read_multi`
on the Rails cache store.
Some caching implementations have optimized `read_multi` so we don't have
to check in the cache store for every template.
|
| | |
|
|\ \
| | |
| | |
| | | |
mail_to helper method fix
|
| | |
| | |
| | |
| | |
| | | |
when mail_to generate blank options for any passed options(cc, bcc, body, subject)
then MICROSOFT OUTLOOK treats it differently and set wrong values in different options.
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
Rename default_form_builder to avoid collision
|
| |/ / |
|
| | |
| | |
| | |
| | | |
The 'selected' option is not doing what it should do.
The expected behavior is to pass the value selected by default for the options_from_collection_for_select method
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Per DHH in #18337, ActionView::Helpers::RecordTagHelper has been
extracted to an external gem (source currently lives at
todd/record_tag_helper). Removal notices have also been added for anyone
upgrading that use the extracted methods.
|
| |/
|/|
| |
| | |
This makes the behavior more consistent with `width` or `height` options
|
|\ \
| | |
| | | |
Remove some code duplication in ActionView tags code
|
| | | |
|
|/ /
| |
| |
| |
| |
| | |
This removes the following warning:
/GitHub/rails/actionview/lib/action_view/helpers/tags/translator.rb:19: warning: private attribute?
|
| |
| |
| |
| |
| | |
Refactoring at #18647 broke using non active record objects in form_for. This patch
restores the original behaviour where we only compute i18 key when object.respond_to?(:to_model)
|
| |
| |
| |
| |
| |
| | |
The `link_to` helper generates an HTML anchor element (consisting of opening and closing anchor tags and an element body). The docs currently state the a link tag is generated (which would indicate a tag like `<link>`, which is another valid HTML tag), so this change clarifies that an anchor element is actually generated.
[ci skip]
|
| |
| |
| |
| | |
call is too generic
|
| | |
|
| | |
|
| |
| |
| |
| | |
Thse methods are used only inside this class
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | | |
The `model_name` method should be called on `to_model`
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
onwards.
|
|/ / |
|
| |
| |
| | |
[ci skip]
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
While we don't want to change the form input when validations fail,
blindly using `_before_type_cast` will cause the input to display the
wrong data for any type which does additional work on database values.
|
| |
| |
| |
| | |
This reverts commit 787e22bb491bd8c36db1e9734261c4ce02c5c5fd.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We should never be ignoring valuable information that the types may need
to give us. The reason that it originally used `_before_type_cast` is
unclear, but appears to date back long enough that the reasons may not
be relevant today. There is only one test that asserts that it uses the
before type cast version, but it gives no context as to why and uses a
mock which does not simulate the real world.
Fixes #18523.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
tigrish/fix_custom_i18n_exception_handler_regression
Fix I18n regression introduced by #13832
|
| | |
| | |
| | |
| | | |
Previously, when the `:raise` options was set to `false`, it would get overwritten to `true`, preventing custom exception handlers to be used.
|