> Yes we could do that. The question in this case is whether we want to > distinguish between around filters returning false and filters that simply > don't yield w.r.t. after filter processing. > > we could say that an around filter returning false will stop after filter > processing whereas filters that simply don't yield will not stop the after > filter chain. > > and while we're at it: I suggest that it should be possible for after > filters to stop after filter chain processing by returning false.
So assuming I've got this right, failing to yield halts the before/around filter chain, prevents the action from rendering but still runs the after filters. Failing to yield and returning false will behave as above, but *not* run the after filters. Does anyone have any objections to this? -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
