Jo Hund

@carlosescri using `filterrific` as name for the param is an important convention that has implications through large parts of filterrific. Allowing to override the name would make the code significantly...

@lastobelus I'm curious to learn how `#request.path_parameters[:controller]` is more reliable than `#controller_name`. What's the difference between the two? Is your concern that `#controller_name` doesn't return namespaces? What if we use...

@gearoidoceallaigh thanks for using Filterrific. Currently there is no simple way to prevent the autoconversion. I'd suggest you prefix it with something like '_' (underscore). That will prevent the casting...

@tscung filterrific inputs by default submit the form on change. I have a hunch that your slider library updates the field value as you move it, and at every change,...

@octant great suggestion. I have thought about this in the past but never got around to implementing it. I think it's possible and I can add this to filterrific pretty...

@octant sorry for the delay on this. I was traveling last week and am kind of stuck on what to do if a filterrific default param is given as a...

@alankessler great idea on the `#applied_filters` method. I'm thinking of implementing 'dirty' object tracking on the `@filterrific` object. If `@filterrific` is initialized with the defaults, it's considered clean. If it's...

@alankessler unfortunately I haven't resolved this yet. I could use it in one of my other [open source projects](https://github.com/jhund/rails-data-explorer). So the motivation is there, it's just not super high on...

@alankessler I started working on this, and then got stuck on how to handle Procs as default values. I'm sure I can figure it out, just need to sit down...

Are you sure that the Filterrific gem is loaded? Are you using Bundler, and did you add Filterrific to your Gemfile?