yt 0.5.13 → 0.5.14

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: bc79b5682be98448f4c2ad0e47e025ece396f2ca
-  data.tar.gz: 3b3ba9a7646c1fe350c10bf1cc01ffc9e3c01062
+  metadata.gz: cc8bf39c826412cf4ebac40de897b1e6d298d3db
+  data.tar.gz: 56a50c740682435e1cf6640e13b1f456f85f7ef7
 SHA512:
-  metadata.gz: e8be6da305362d7f2578157ba5cdd0d6c717bbbd8f5a677ac898af79332fc5bb098b0f777006fc7d002da696346403910d724c673e308d897b1c700fa83e295e
-  data.tar.gz: 90842585d61ad708d4dba3fefac8b7bc2f51ac8eeae58ca3acdd5d989bf4eae495ba9a6b984b758f4e7bc5f2b20a5d8f14604c6e821ecb935745af67fb5363c8
+  metadata.gz: f23bdaf43476b944abfe8a0614cd381f4a340929aee7e480425a07f62ce4dbed0e76d5e65b4f15e22a4098fdee392de0b9e4b39492ddb4c28cb9fdab60ea2fa0
+  data.tar.gz: 5a3629db8476e76a4a37dbbb457f85a43a800149d7f31d8f9eb16cec181ee6d8f2be5ed5c5bb4e0dfa049750b3a919104cff4ad905f4d59d513d90eeafa0d9ce

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    yt (0.5.13)
+    yt (0.5.14)
       activesupport
 
 GEM

data/README.md

@@ -10,7 +10,7 @@ Yt helps you write apps that need to interact with the YouTube API V3.
 [![Code Climate](https://codeclimate.com/github/Fullscreen/yt.png)](https://codeclimate.com/github/Fullscreen/yt)
 [![Inline docs](http://inch-pages.github.io/github/Fullscreen/yt.png)](http://inch-pages.github.io/github/Fullscreen/yt)
 
-After [registering your app](#registering-your-app), you can run commands like:
+After [registering your app](#configuring-your-app), you can run commands like:
 
 ```ruby
 channel = Yt::Channel.new id: 'UCxO1tY8h1AhOz0T4ENwmpow'
@@ -226,8 +226,8 @@ so you won’t be able to like a video, subscribe to a channel or delete a
 playlist from a specific account. You will only be able to retrieve read-only
 data.
 
-Web apps that do require user interactions
-------------------------------------------
+Web apps that require user interactions
+---------------------------------------
 
 If you are building a web app that manages YouTube accounts, you need the
 owner of each account to authorize your app. There are three scenarios:
@@ -287,52 +287,10 @@ account.email #=> (retrieves the account’s e-mail address)
 account.playlists.first.add_video 'MESycYJytkU' #=> (adds a video to an account’s playlist)
 ```
 
-Device apps that do require user interactions
----------------------------------------------
-
-These apps are equivalent to web apps. The only difference is the interface
-that Google uses to ask people to authenticate.
-
-
-Scenario 1. If you already have the account’s **access token**, then you are ready to go.
-Just pass that access token to the account initializer, such as:
-
-```ruby
-account = Yt::Account.new access_token: 'ya29.1.ABCDEFGHIJ'
-account.email #=> (retrieves the account’s e-mail address)
-account.playlists.first.add_video 'MESycYJytkU' #=> (adds a video to an account’s playlist)
-```
-
-Scenario 2. If you don’t have the account’s access token, but you have the
-**refresh token**, then it’s almost as easy.
-Open the [Google Developers Console](https://console.developers.google.com),
-find the client ID and client secret of the **native application** that you used to obtain the
-refresh token, then add the following snippet of code to the initializer of your app:
-
-```ruby
-Yt.configure do |config|
-  config.client_id = '1234567890.apps.googleusercontent.com'
-  config.client_secret = '1234567890'
-end
-```
-
-replacing the values above with the client ID and secret for web application.
-Then you can manage a YouTube account by passing the refresh token to the
-account initializer, such as:
-
-```ruby
-account = Yt::Account.new refresh_token: '1/1234567890'
-account.email #=> (retrieves the account’s e-mail address)
-account.playlists.first.add_video 'MESycYJytkU' #=> (adds a video to an account’s playlist)
-```
-
-Scenario 3. If you don’t have the account’s refresh token, then [..TODO..]
-
-
-Configuring your app through environment variables
-==================================================
+Configuring with environment variables
+--------------------------------------
 
-As an alternative to the approach above, you can configure Yt using environment
+As an alternative to the approach above, you can configure your app with
 variables. Setting the following environment variables:
 
 ```bash
@@ -342,7 +300,7 @@ export YT_CLIENT_SECRET="1234567890"
 export YT_API_KEY="123456789012345678901234567890"
 ```
 
-is equivalent to configuration your app with the initializer:
+is equivalent to configuring your app with the initializer:
 
 ```ruby
 Yt.configure do |config|
@@ -365,7 +323,7 @@ To install on your system, run
 
 To use inside a bundled Ruby project, add this line to the Gemfile:
 
-    gem 'yt', '~> 0.5.13'
+    gem 'yt', '~> 0.5.14'
 
 Since the gem follows [Semantic Versioning](http://semver.org),
 indicating the full version in your Gemfile (~> *major*.*minor*.*patch*)

data/lib/yt/collections/authentications.rb

@@ -9,6 +9,7 @@ module Yt
     private
 
       def new_item(data)
+        data['refresh_token'] = auth_params[:refresh_token]
         Yt::Authentication.new data
       end
 

data/lib/yt/version.rb

@@ -1,3 +1,3 @@
 module Yt
-  VERSION = '0.5.13'
+  VERSION = '0.5.14'
 end

data/spec/associations/device_auth/authentications_spec.rb

@@ -11,6 +11,7 @@ describe Yt::Associations::Authentications, :device_app do
       context 'that is valid' do
         let(:refresh_token) { ENV['YT_TEST_DEVICE_REFRESH_TOKEN'] }
         it { expect(account.authentication).to be_a Yt::Authentication }
+        it { expect(account.refresh_token).to eq refresh_token }
       end
 
       context 'that is invalid' do

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: yt
 version: !ruby/object:Gem::Version
-  version: 0.5.13
+  version: 0.5.14
 platform: ruby
 authors:
 - Claudio Baccigalupo
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-06-04 00:00:00.000000000 Z
+date: 2014-06-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport