Change uid to account_id due to shutdown of API v1

[mendab1e]

Hello. Dropbox API v1 was shutdown on September 28th, 2017. Here is a note from the migration guide:

In v1, user accounts included a uid field, an integer that represented a user's Dropbox ID. In v2, we use account_id, which is a string that represents the user's unique Dropbox ID.

In this pull request uid was replaced with account_id to update the gem for API v2. Also double quotes without interpolation were replaced with single quotes.

[mendab1e]

Ping @bamorim

[nitanshu]

Hi, @mendab1e have you fixed this gem for Dropbox API v2 ?

[mendab1e]

@nitanshu yes, works fine with v2 for me.

[bamorim]

Guys, I'm sorry. Does anyone wants to maintain this gem? I'm short in time. I can give the access on the rubygems as well. Sorry about that, Bernardo

…

On Nov 11, 2017 1:38 PM, "Timur" ***@***.***> wrote: @nitanshu <https://github.com/nitanshu> yes, works fine with v2 for me. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAyisRQZq02lJoikD8yHRc8U-9PBrzgBks5s1b-QgaJpZM4PsH2k> .

[mendab1e]

@bamorim I don't have much experience in maintaining public gems, but I can try.

[nitanshu]

@bamorim @mendab1e Hi Guys, I tried this gem with latest code not working for me I got Error 400 invalid client id but is this mandatory to use omniauth-oauth2 ~> 1.3.1 instead of 1.4.0

[hugofloss]

@bamorim Yes, I'd like to maintain this gem and get permissions for this repo and RubyGems. I'm also the maintainer of another OmniAuth plugin, so it's not new to me. Should I email you?