Philippe Monnet
2010-Apr-18 23:01 UTC
Should we incorporate a filtering mechanism in controllers?
Last year I discovered filtering_camping <http://github.com/judofyr/filtering_camping> and I have been using it in my apps. As I am working on a OAuth Camping plugin (adapted from the OAuth Rails plugin), I was thinking of using filtering_camping. And that lead to the following questions? 1. Are people using filtering_camping? 2. Are people using other types of before/after filter framework? 3. Should we incorporate this capability in the base? 4. Do people prefer something simple dead easy like filtering_camping? Or would people prefer something more like filters in Rails? Philippe -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20100418/ec315c0a/attachment-0001.html>
Dave Everitt
2010-Apr-19 09:56 UTC
Should we incorporate a filtering mechanism in controllers?
Philippe - dead simple for me. I was put off Rails a long time ago, which is how I landed on Camping - Dave Everitt> Do people prefer something simple dead easy like filtering_camping? > Or would people prefer something more like filters in Rails?
Magnus Holm
2010-May-31 15:20 UTC
Should we incorporate a filtering mechanism in controllers?
Hm? Camping already has filters: module App def service(*a) # before super ensure # after end end I''m not sure if we need to add another way to support filters? // Magnus Holm On Mon, Apr 19, 2010 at 11:56, Dave Everitt <deveritt at innotts.co.uk> wrote:> Philippe - dead simple for me. I was put off Rails a long time ago, which is > how I landed on Camping - Dave Everitt > >> Do people prefer something simple dead easy like filtering_camping? Or >> would people prefer something more like filters in Rails? > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list >