From b047929c14f088d535eea460ddd8769f43cd4ae5 Mon Sep 17 00:00:00 2001 From: Pratik Naik Date: Sun, 2 Nov 2008 04:02:40 +0530 Subject: Merge with docrails --- railties/doc/guides/source/actioncontroller_basics/filters.txt | 2 -- 1 file changed, 2 deletions(-) (limited to 'railties/doc/guides/source/actioncontroller_basics') diff --git a/railties/doc/guides/source/actioncontroller_basics/filters.txt b/railties/doc/guides/source/actioncontroller_basics/filters.txt index a7b8d9727f..a6f688d144 100644 --- a/railties/doc/guides/source/actioncontroller_basics/filters.txt +++ b/railties/doc/guides/source/actioncontroller_basics/filters.txt @@ -55,8 +55,6 @@ Now, the LoginsController's "new" and "create" actions will work as before witho In addition to the before filters, you can run filters after an action has run or both before and after. The after filter is similar to the before filter, but because the action has already been run it has access to the response data that's about to be sent to the client. Obviously, after filters can not stop the action from running. Around filters are responsible for running the action, but they can choose not to, which is the around filter's way of stopping it. -TODO: Find a real example for an around filter - [source, ruby] --------------------------------- # Example taken from the Rails API filter documentation: -- cgit v1.2.3