| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
`rails:update` was deprecated in 6fb31638c8b61731103d4963272755b217a2df87
|
|\
| |
| | |
[ci skip] Add small Action Cable documentation fixes
|
| |
| |
| |
| |
| | |
* Fix typos/grammar errors
* Make capitalization/naming consistent
|
|/
|
|
|
|
|
|
|
|
|
|
| |
This guides were pointing to this command `rails app:update`, which I
tried to run, but it didnt worked. I think the right command is `rails
rails:update` instead. Also thats the name of the rake task.
Also I removed the `Rake` word from the title, as we run it using
`rails` bin now.
cc @kaspth
[skip ci]
|
|\
| |
| | |
Use app namespace for framework tasks
|
| |
| |
| |
| | |
(e.g. `rails:update` and `rails:template` tasks is renamed to `app:update` and `app:template`.)
|
|/
|
|
| |
refer 2dc3e81aea8dbc, 56ca2061df83a3
|
|\
| |
| | |
Changed debugging rails app doc.
|
| |
| |
| |
| |
| |
| | |
Changed location for specifying logger.
[Prajakta, thiagoaugusto]
|
| |
| |
| |
| | |
[ci skip]
|
| |
| |
| |
| | |
[ci skip]
|
|\ \
| | |
| | | |
[ci skip] Update configuration guide
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
* Fixes typos in error message and release notes.
* Removes unused template test file.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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]
|
| |
| |
| |
| | |
This also marks Action Cable routes as internal to Rails.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
|\ \
| | |
| | | |
Changes caching guide to add note on weak etags
|
| | | |
|
|\ \ \
| | | |
| | | | |
[ci skip] Update guide sources for mailer view caching feature
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
| |/| |
|
|/ /
| |
| |
| | |
Adds changelog headers for beta3 release
|
|\ \
| | |
| | | |
AppGenerator: Replace 'rake' with 'rails_command'
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since Rails 5.0 is switching the Rails command line from 'rake …'
to 'rails …', it makes sense to also replace the `rake` method in
the Rails templates API.
Based on feedback from @matthewd and @kaspth, I chose to replace
`rake` with `rails_command`, which is less confusing than
the alternatives `rails` or `command` or `rails_run` and is not
Thor-reserved word like `task`.
|
|\ \ \
| | | |
| | | | |
Turbolinks 5 compatibility changes
|
| | | | |
|
| | |/
| |/| |
|
| | | |
|
|/ / |
|
| | |
|
|/
|
| |
This is a notable change since this will cause confusing test failures for tests relying on the old naming scheme.
|
|
|
|
|
| |
Since a0343d11f1bf80a79e273c1d0cf9934ef2601e98, `debug_exception_response_format` config depends on `api_only`.
Therefore, if set the `api_only`, need to specify `debug_exception_response_format` is not.
|
| |
|
|
|
|
|
| |
All gems are released now so we don't need to ask the github repository
for these gems anymore.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
and DateTime
[ci skip] Adding `on_weekend?` method in edge rails guides
|
|
|
|
|
|
|
|
|
| |
Whenever you are sending emails in integration tests using the `:test`
delivery method you need to make sure that
`ActionMailer::Base.deliveries` is reset after every test. This piece of
boilerplate code is present in all my applications that send
emails. Let's have `ActionDispatch::IntegrationTest` reset the
deliveries automatically.
|
|\
| |
| | |
Fix small typo in i18n guide [ci skip]
|
| | |
|
|\ \
| |/
|/| |
Add `#on_weekday?` method to `Date`, `Time`, and `DateTime`.
|
| | |
|
|/ |
|