> Does positive feedback for this change mean you'll consider dropping the old > way of halting filters? Personally I've never felt that "false" was a bad > value and I liked that it was chosen for halting. I don't think it has ever > inadvertently halted the chain for me -- really, what are the chances of > putting a method that returns boolean as the last statement in a filter?
Returning false will no longer halt the chain. It never really made any sense to halt the chain without rendering or redirecting, it only lead to White Screens of Death. Plenty of people were bitten by it. This is now fact from http://dev.rubyonrails.org/changeset/7984 and forth. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
