Add keywords to handle additional fields in API response#3
Add keywords to handle additional fields in API response#3alextsui05 wants to merge 12 commits intoR167:masterfrom
Conversation
|
Thank you very much for this! I have really been meaning to get this gem to a stable and more compliant state, but over the last few months, life has been catching up with me. I'll absolutely look over this in the morning when I have time. Hopefully, it works with the changes I'd been testing in my |
|
@R167 Glad to hear your reply! I'm trying to see how much work to fold in the commits from the Maybe there was a file that wasn't committed? If you'd like, we can try to get the error squared away and I can do some tests, then I'll update my master branch so we can see all the changes at a glance here. |
Remove :b2_bucket option, replace with `bucket` key in the credentials file
Thank you for your work on this useful gem!
I was testing out the API and was getting some errors where there were more keys being passed to the constructor of B2::Bucket and B2::File than expected. Maybe the response has gained a few new fields recently:
I also added an alias to B2::Bucket#bucket_name because I was getting this error in B2::File#download_url
While I was at it, I added a
first_filekeyword for B2::Bucket#file_names so you can search a bucket by filename.By the way, I am working on a paperclip gem using the
backblazegem as a base, and I was stuck on how to provide support for creating B2::Files from Paperclip's file adapter. Let me know if you'd be interested, it would be great to have your feedback.