Commit afdc7776 by slainer68

loosen rails version

parent b3edf94e
......@@ -3,7 +3,7 @@ source "https://rubygems.org"
gemspec
gem 'pry'
gem 'rails', '~> 4.1.4'
gem 'rails', '>= 3.2.0'
platforms :rbx do
gem 'racc'
......
......@@ -9,12 +9,10 @@ REST conventions take the guesswork out of designing and consuming web APIs. Sim
However, when it comes to figuring out what parameters are expected... well, all bets are off.
This Rails extension takes a first step to solving this problem on the developer side
This Rails extension takes a first step to solving this problem on the developer side.
**`rails-param` allows you to declare, validate, and transform endpoint parameters as you would in frameworks like [ActiveModel](http://rubydoc.info/gems/activemodel/3.2.3/frames) or [DataMapper](http://datamapper.org/).**
> Use `rails-param` in combination with [`Rack::PostBodyContentTypeParser` and `Rack::NestedParams`](https://github.com/rack/rack-contrib) to automatically parameterize JSON `POST` bodies and nested parameters.
## Example
``` ruby
......
......@@ -12,10 +12,10 @@ Gem::Specification.new do |s|
s.license = 'WTFPL'
s.description = %q{
Parameter Validation & Type Coercion for Rails
Parameter Validation and Type Coercion for Rails
}
s.summary = 'Parameter Validation & Type Coercion for Rails'
s.summary = 'Parameter Validation and Type Coercion for Rails'
s.required_rubygems_version = '>= 1.3.6'
......@@ -26,6 +26,6 @@ Gem::Specification.new do |s|
s.add_development_dependency 'rspec', '~> 2.11'
s.add_development_dependency 'rspec-rails', '~> 2.11'
s.add_development_dependency 'actionpack', '>= 4.1.0'
s.add_development_dependency 'activesupport', '>= 4.1.0'
s.add_development_dependency 'actionpack', '>= 3.2.0'
s.add_development_dependency 'activesupport', '>= 3.2.0'
end
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment