| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Doc: update guides for Rails 5
|
| |
| |
| |
| | |
[ci skip]
|
|/
|
|
| |
[ci skip]
|
|\
| |
| | |
[ci skip] Update configuration guide
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
* Fixes typos in error message and release notes.
* Removes unused template test file.
|
|\ \
| |/
|/| |
Lock down new `ImplicitRender` behavior for 5.0 RC
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Conceptually revert #20276
The feature was implemented for the `responders` gem. In the end,
they did not need that feature, and have found a better fix (see
plataformatec/responders#131).
`ImplicitRender` is the place where Rails specifies our default
policies for the case where the user did not explicitly tell us
what to render, essentially describing a set of heuristics. If
the gem (or the user) knows exactly what they want, they could
just perform the correct `render` to avoid falling through to
here, as `responders` did (the user called `respond_with`).
Reverting the patch allows us to avoid exploding the complexity
and defining “the fallback for a fallback” policies.
2. `respond_to` and templates are considered exhaustive enumerations
If the user specified a list of formats/variants in a `respond_to`
block, anything that is not explicitly included should result
in an `UnknownFormat` error (which is then caught upstream to
mean “406 Not Acceptable” by default). This is already how it
works before this commit.
Same goes for templates – if the user defined a set of templates
(usually in the file system), that set is now considered exhaustive,
which means that “missing” templates are considered `UnknownFormat`
errors (406).
3. To keep API endpoints simple, the implicit render behavior for
actions with no templates defined at all (regardless of formats,
locales, variants, etc) are defaulted to “204 No Content”. This
is a strictly narrower version of the feature landed in #19036 and
#19377.
4. To avoid confusion when interacting in the browser, these actions
will raise an `UnknownFormat` error for “interactive” requests
instead. (The precise definition of “interactive” requests might
change – the spirit here is to give helpful messages and avoid
confusions.)
Closes #20666, #23062, #23077, #23564
[Godfrey Chan, Jon Moss, Kasper Timm Hansen, Mike Clark, Matthew Draper]
|
|\
| |
| | |
Only hijack Rack socket when first needed
|
| |
| |
| |
| | |
Fixes #23471
|
|\ \
| | |
| | | |
Fix README heading according to Markdown conventions
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The first heading in some README's are indicated using a second level
heading (`##`), which in my opinion is of incorrect structure.
Therefore, in this patch I changed the first heading to a first level
heading (`#`) in README's where this incorrect structure occurs.
[ci skip]
|
|\ \ \
| |_|/
|/| | |
Enable ActionCable routes by default
|
| | | |
|
| | |
| | |
| | |
| | | |
This also marks Action Cable routes as internal to Rails.
|
|\ \ \
| |/ /
|/| | |
Added a test for generating Strong ETag
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
akshaymohite/api-app-debug-exception-response-format-in-doc
[ci skip] Need to mention debug_exception_response_format in the api_app documentation.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
documentation.
- #23771 removed the reference to debug_exception_response_format from the api_app documentation.
- We need to let users know, they have ability to configure debug_exception_response_format in their development environment.
- Added documentation for the same in api_app.md file
- Grammar corrections
|
|\ \ \
| | | |
| | | | |
[ci skip] Replace usage of rake routes with rails routes
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I ran into an issue where validations on a suppressed record were
causing validation errors to be thrown on a record that was never going
to be saved.
There isn't a reason to run the validations on a record that doesn't
matter.
This change moves the suppressor up the chain to be run on the `save` or
`save!` in the validations rather than in persistence. The issue with
running it when we hit persistence is that the validations are run
first, then we hit persistance, and then we hit the suppressor. The
suppressor comes first.
The change to the test was required since I added the
`validates_presence_of` validations. Adding this alone was enough to
demonstrate the issue. I added a new test to demonstrate the new
behavior is explict.
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* master: (113 commits)
remove useless method
Updated file documentation [ci skip]
changes caching guide to add note on weak etags
Don't put config.action_mailer.perform_caching entry twice in development.rb
Fix wording and wrong reference
Add Ruby formatting to CHANGELOG entry
Fix ActionView's cache section reference
Do not define methods in the included block
Add caching guide in ActionMailer basics
Add ActionMailer configuration options
Preparing for 5.0.0.beta3 release
Update 5.0 release notes
Enable tmp_restart plugin for puma
Prep release for Rails 5 beta3
[ci skip] Move collection caching changelog entry.
Ensure `drop_table` even if tests failure or interrupted
:bomb: run the test @rafaelfranca :angry:
Remove changelog entry for reverted commit
Add CHANGELOG for https://github.com/rails/rails/pull/23734 [ci skip]
No need CHANGELOG entry for #23849.
...
|
| | | | |
|
| |\ \ \
| | |/ /
| |/| | |
Updated file documentation [ci skip]
|
| |/ / |
|
| |\ \
| | | |
| | | | |
Changes caching guide to add note on weak etags
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
prathamesh-sonpatki/dont-put-perform-caching-config-twice
Don't put config.action_mailer.perform_caching entry twice in development.rb
|
| | | | | |
|
| |\ \ \ \
| | |/ / /
| |/| | | |
[ci skip] Update guide sources for mailer view caching feature
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | | |
| | | | | | |
Add Ruby formatting to CHANGELOG entry
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
[ci skip]
|
| | | | |
| | | | |
| | | | |
| | | | | |
Instance methods can be defined in the module itself
|
| | | | |
| | | | |
| | | | |
| | | | | |
Adds changelog headers for beta3 release
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes #23855
|
| |/ / / |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We changed this in beta2, and only editing the original entry means
people can't see that it was significantly changed.
|
| |\ \ \
| | | | |
| | | | | |
Ensure `drop_table` even if tests failure or interrupted
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I was encountered remaining `:binary_testings` table by tests failure.
When remaining `:binary_testings` table, never reach `drop_table` due to
`create_table` in the test always fails.
|
| |/ / / |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
I had to revert changes made for this CHANGELOG entry so this is no
longer valid. The change for this entry was removed in 2c02bc0.
|
| |\ \ \
| | | | |
| | | | | |
Add CHANGELOG for https://github.com/rails/rails/pull/23734 [ci skip]
|
| |/ / / |
|