aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorRafael França <rafaelmfranca@gmail.com>2017-03-29 13:08:02 -0400
committerGitHub <noreply@github.com>2017-03-29 13:08:02 -0400
commit2d0d611c4db9ec63c9fdb602a95461acb5c44539 (patch)
treebc759becb4ec7b495ea3a9feb5867160b7e3d283 /guides
parenteccc149be362ccf12446ed1c8287e011731a817b (diff)
parent2b3a3738b7a519f32f593f6e6b9c6ba89daa72ea (diff)
downloadrails-2d0d611c4db9ec63c9fdb602a95461acb5c44539.tar.gz
rails-2d0d611c4db9ec63c9fdb602a95461acb5c44539.tar.bz2
rails-2d0d611c4db9ec63c9fdb602a95461acb5c44539.zip
Merge pull request #28595 from 3wille/fw-after-action-hint
add hint on after_action filters
Diffstat (limited to 'guides')
-rw-r--r--guides/source/action_controller_overview.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/action_controller_overview.md b/guides/source/action_controller_overview.md
index 69c4a00c5f..a43a69b7a3 100644
--- a/guides/source/action_controller_overview.md
+++ b/guides/source/action_controller_overview.md
@@ -719,7 +719,7 @@ Now, the `LoginsController`'s `new` and `create` actions will work as before wit
In addition to "before" filters, you can also run filters after an action has been executed, or both before and after.
-"after" filters are similar to "before" filters, but because the action has already been run they have access to the response data that's about to be sent to the client. Obviously, "after" filters cannot stop the action from running.
+"after" filters are similar to "before" filters, but because the action has already been run they have access to the response data that's about to be sent to the client. Obviously, "after" filters cannot stop the action from running. Please note that "after" filters are executed only after a successful action but not when an exception was raised in the request cycle.
"around" filters are responsible for running their associated actions by yielding, similar to how Rack middlewares work.