stffn/declarative_authorization — pull request #194 by zeiv (2014-07-03 21:23:22+00:00)
Title: Rails 4 support

### Main Changes:###
* Updates test suite for Rails 4.0 (4.1 uses Minitest, however)
* Adds route compatibility for Rails 4
* Adds gemfile for Rails 4.0
* Updates analyzer (tests pass, no more no method `shift' error): closes #174 and closes #185
* Remove deprecated link_to_function and button_to_function from from development support
* Removes deprecated `unloadable` method
* Strong Parameters support: closes #184

### Tested On:###
* Rails 2.3.18 (Ruby 1.8.7-p374)
* Rails 3.2.16 (Ruby 1.9.3-p484)
* Rails 4.0.2 (Ruby 2.1.2)
* ___All tests passing___

For strong_parameters, I added a `:strong_parameters` option to `filter_resource_access` that accepts a boolean. It defaults to try on rails > 4 and false on rails < 4. When `:strong_parameters` is enabled, declarative_authorization __will not__ create a new object or set an instance variable for the `create` action because strong_parameters's use of a private method to sanitize parameters expects that the object will be created in the original controller. This patch will, however, create an empty object for the instance variable of `new` actions.

:exclamation:__IMPORTANT NOTE__:exclamation:
I have silenced deprecation warnings in the test suite for Rails 4. Work still has to be done with some deprecated features like `Model.scoped` and eager loading.