xzzz9097/spotifykit

Swift client for Spotify Web API

spotifykit's Issues

Is there any way to de-authorize (log out)?

C

Using SpotifyKit to export playlists

I'm a complete beginner to Swift but wanted to create an app that exports playlists to Spotify based on mood. I have a random array of Spotify song URI strings but for some reason, I cannot 1) connect the user to my app (ie: based on your test code, the picture and information do not update) and 2) figure out how to export a playlist.

If you could briefly explain how I could do that, I would really appreciate it.

OAuth Token Now Required To Search Spotify

Spotify updated their API and is now requiring an OAuth token to use the Search endpoint:
https://developer.spotify.com/web-api/console/get-search-item/

swiftify.find will need to be updated to include the user's token in the GET request.

Feature: A-B repeat / Loop snippet of Spotify song track

Hi -
What nice idea (building an API/SDK around Spotify web)! I wonder if you've also exposed enough low-level detail to invoke useful features like "play again from 15 seconds ago" and actual looping of a predefined section?

Best way to describe the song looping is in this unrealized, fairly popular Spotify feature request:
https://community.spotify.com/t5/Closed-Ideas/Music-Looping-individual-Songs-or-Parts/idi-p/1551156

Replace Alamofire with URLSession

For our needs an extended implementation of URLSession should be more than enough, allowing to remove Alamofire dependency.

Accepting pull requests?

Hello! I have been using SpotifyKit for my own personal project, but saw it didn't meet all of my use cases. So of course I added some of my own needed features such as spotify pagination, auth scopes,and completion handler for after authentication (just to name a few). I would be happy to clean it up a bit and submit a request. It's a bit messy but feel free to take a look here

Use Swift's (De)Codable Interfaces instead of SwiftyJSON

Since Swift 4 can now natively de- and encode JSON it might be a nice way to reduce dependencies, using the built in methods going forward. I'd be happy to help if you need assistance :)

Podfile integration issues

Hi,

Thanks for the nice framework. A couple issues:

I create a fresh single view project using the latest Xcode, compiled for iOS12. I then integrated into this project using:

pod 'SpotifyKit'

I receive a compilation error, and the framework appears in red within the project. This is using the master branch 0.0.6

I instead grabbed the source and placed in the project (in lieu of pod file integration) and receive two warnings in iOS12.

'unarchiveObject(with:)' was deprecated in iOS 12.0: Use +unarchivedObjectOfClass:fromData:error: instead

These occur on lines 35 and 55 in file Keychain.swift

Would appreciate if you could guid me on proper Pod integration, and whether I am pointing to the proper version. As I noticed you have a Swift4 branch, though your comments in the main branch allude to swift4 integration.

Thanks again.

Future development question

Thanks for this library, I was playing around with it and found it very useful.

So far I had the following problems:

• missing fields in data parsing (ex. external_urls, external_ids etc.)
• error handling seems to be missing on malformed responses
• Unaccessible private properties on data models (ex. images)
• Missing data models (ex. category)

Overall the parsing contains very good ideas with generic models and it was a great way getting into Decodables.

I mainly used SpotifyItems, cleaned it up, added a generic collection item that could be reused across all responses containing paginated lists (parsing all fields: limit, offset, total, prev, next) and some readability improvements.

My question:
Is there a plan to improve this library in the future?
Would pull requests be considered?

Many thanks.