Conversation
|
On the subject of breaking changes, what do you think about removing the .results object from the response. Currently it works like this: songs = itunes.music('green day she')
songs.results.each do |song|
puts "#{song.track_name} - #{song.artist_name} (#{song.collection_name})"
endI don't think the result payloads include anything worth keeping (AFAIK just a result_count which is basically the same thing as songs = itunes.music('green day she')
songs.each do |song|
puts "#{song.track_name} - #{song.artist_name} (#{song.collection_name})"
end |
|
Do you have other music services in mind to add to this? |
|
I was thinking Spotify or Last.fm would be good additions. That way you could search multiple databases (with the obvious overhead of multiple requests). > Tunes.sources
# => [Tunes::Source::ITunes, Tunes::Source::Spotify, Tunes::Source::LastFm]
> Tunes.sources = :spotify
> Tunes.sources
# => [Tunes::Source::Spotify]
> Tunes.sources << :lastfm
# => [Tunes::Source::Spotify, Tunes::Source::LastFm] |
|
Sweet! This was actually one of my original motivators with this gem. In particular, I wanted to be able to search across iTunes and Amazon for availability/price. I could see a similar desire to do so with Spotify/Rdio/etc. |
|
+1 for @spagalloco point on "flattening" |
Just starting the renaming so it'll be ready if we decide to change the module name.