Skip to content
Browse files

Changed the requirement for json to 1.6.5

  • Loading branch information...
1 parent b998e42 commit 2e53874ffd3bd32966d4928ec3a7cacfa291fe9d @economysizegeek economysizegeek committed Sep 20, 2012
Showing with 9 additions and 5 deletions.
  1. +1 −0 Gemfile
  2. +5 −4 Gemfile.lock
  3. +1 −1 insightly.gemspec
  4. +2 −0 lib/insightly/base.rb
View
1 Gemfile
@@ -1,5 +1,6 @@
source :rubygems
gem 'i18n' , "~> 0.5.0"
+gem 'json',"=1.6.5"
gemspec
gem 'rspec'
gem 'rake'
View
9 Gemfile.lock
@@ -1,11 +1,11 @@
PATH
remote: .
specs:
- insightly (0.2.2)
+ insightly (0.2.3)
activesupport (> 3)
builder (>= 2.0.0)
i18n (> 0)
- json (>= 1.7.5)
+ json (>= 1.6.5)
logger (>= 1.2.8)
rest-client (>= 1.6.7)
@@ -18,7 +18,7 @@ GEM
diff-lcs (1.1.3)
gemcutter (0.7.1)
i18n (0.5.0)
- json (1.7.5)
+ json (1.6.5)
logger (1.2.8)
mime-types (1.19)
multi_json (1.2.0)
@@ -32,7 +32,7 @@ GEM
rspec-core (2.11.1)
rspec-expectations (2.11.3)
diff-lcs (~> 1.1.3)
- rspec-mocks (2.11.2)
+ rspec-mocks (2.11.3)
PLATFORMS
ruby
@@ -41,5 +41,6 @@ DEPENDENCIES
gemcutter
i18n (~> 0.5.0)
insightly!
+ json (= 1.6.5)
rake
rspec
View
2 insightly.gemspec
@@ -12,7 +12,7 @@ Gem::Specification.new do |s|
s.has_rdoc = false
s.files = Dir.glob ["README.md", "LICENSE", "{lib,spec}/**/*.rb", "lib/**/*.crt", "*.gemspec"]
s.add_dependency "builder", ">= 2.0.0"
- s.add_dependency "json", ">= 1.7.5"
+ s.add_dependency "json", ">= 1.6.5"
s.add_dependency "rest-client", ">= 1.6.7"
s.add_dependency "logger", ">= 1.2.8"
s.add_dependency "activesupport", "> 3"
View
2 lib/insightly/base.rb
@@ -1,5 +1,7 @@
#METODO contacts allow you to set special dates to remember - can we access that via api?
#METODO only allow build to set fields that are part of the API fields
+#METODO Fix all tests so they don't require the existence of certain object ids
+
#METODO make a distinction between fields that you can set and save and ones you can only read - like DATE_UPDATED_UTC
module Insightly
class Base

0 comments on commit 2e53874

Please sign in to comment.
Something went wrong with that request. Please try again.