omniauth-bike-index 0.0.3 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 509ba75c1d01e9e1d081dbd1cb93b21eb7f2b096
-  data.tar.gz: 7d2d56b8868aa2520ecebcdccdcdd54b48dd3dcf
+  metadata.gz: df30b257d96047b03e1d60869233c69ee293bbb0
+  data.tar.gz: ff7734850c1f426614774c7d798a7e54dde7d1c3
 SHA512:
-  metadata.gz: 95307afd2d1044df19940fe18d29d7a24595e086f4fccf4f0ee2032e1804bf5fe774a702b0082c86cc321adf750b266e99ceddb488f088e2ece19dd355845932
-  data.tar.gz: e63efadffafba5bd584d413780d3afe37c9c299193ce9d4ee0b8fccb1a4f1d74a19df4b45e609f9c77bd8b1126b2547cbf084d659bdfc992139f64df0290d2fc
+  metadata.gz: 747feadbb1ed8d937b44f583119d338186e66f4182d319b32691ecc28d67ca8eb3b9e8c0d14d93dc9a5a71ee8a279f4202ecf0c903c1c84c460d11069108d6cd
+  data.tar.gz: 7693d9b2c71430dee0dde1c7ea011c1d21f7751be888acaf62052ba7439f79416307f629e619b7245f4cad1133d70839b69deccb120b74d7851d4780c02ea365

data/.gitignore

@@ -17,4 +17,6 @@ test/version_tmp
 tmp
 .env
 .rspec
-.ruby-*
+.ruby-*
+
+info.markdown

data/README.md

@@ -61,7 +61,7 @@ Devise.setup do |config|
 end
 ```
 
-Available scopes: `read_user`, `write_user`, `read_bikes`, `write_bikes`, `read_bikewise`, `write_bikewise`
+Available scopes: `read_user`, `write_user`, `read_bikes`, `write_bikes`
 
 
 ## Credentials
@@ -72,11 +72,8 @@ If you include the `read_bikes` scope, the response will include an array of the
 
 You can use these IDs to access information about the bikes - e.g. [BikeIndex.org/api/v1/bikes/3414](https://bikeindex.org/api/v1/bikes/3414) & [/api/v1/bikes/29367](https://bikeindex.org/api/v1/bikes/29367)
 
-_currently, you should use the v1 of the API ([documentation](https://bikeindex.org/documentation))_
-
-
-If you include the `read_user` scope, the response will include the user's username, email and name. You will also see their twitter handle and avatar if they have added them. The keys for these items - 
-`username`, `email`, `name`, `twitter` & `image` - all accessible in the `request.env['omniauth.auth']`, e.g. `request.env['omniauth.auth'].info.email`
+If you include the `read_user` scope, the response will include the user's nickname, email and name. You will also see their twitter handle and avatar if they have added them. The keys for these items - 
+`nickname`, `email`, `name`, `twitter` & `image` - all accessible in the `request.env['omniauth.auth']`, e.g. `request.env['omniauth.auth'].info.email`
 
 
 ## Auth Hash

data/lib/omniauth/bike_index/version.rb

@@ -1,5 +1,5 @@
 module OmniAuth
   module BikeIndex
-    VERSION = '0.0.3'
+    VERSION = '0.1.0'
   end
 end

data/lib/omniauth/strategies/bike_index.rb

@@ -12,7 +12,7 @@ module OmniAuth
 
       info do
         prune!(
-          'username'    => raw_info['user']['username'],
+          'nickname'    => raw_info['user']['username'],
           'bike_ids'    => raw_info['bike_ids'],
           'email'       => raw_info['user']['email'],
           'name'        => raw_info['user']['name'],
@@ -33,8 +33,6 @@ module OmniAuth
 
       def request_phase
         options[:authorize_params] = {
-          # :client_id      => options['client_id'],
-          # :response_type  => 'code',
           :scope          => (options['scope'] || DEFAULT_SCOPE)
         }
 

data/spec/app.rb

@@ -20,7 +20,7 @@ end
 
 get '/' do
   <<-HTML
-  <a href='/auth/venmo'>Sign in with Venmo</a>
+  <a href='/auth/venmo'>Sign in with Bike Index</a>
   HTML
 end
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: omniauth-bike-index
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.1.0
 platform: ruby
 authors:
 - Seth Herr
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-01-02 00:00:00.000000000 Z
+date: 2015-04-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: omniauth
@@ -106,7 +106,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.2
+rubygems_version: 2.4.6
 signing_key: 
 specification_version: 4
 summary: Bike Index strategy for OmniAuth