linda-le1 / beet-farmer Goto Github PK

As a developer,
When I receive user input from the front-end,
I am passed the params for cuisine and mood,
And I am able to use them to generate 3 API requests:

• 1: for cuisine playlists (from Spotify)
• 2: for mood playlists (from Spotify)
• 3: for a combo (user-generated)

I am handling edge-cases where the results from any request are =< 4.

• Travis CI: https://travis-ci.org/
• Get TravisCI to show up on PR in Github
• Create Repo

As a developer,
When I receive the results back from an endpoint,
I sample the results to get 5 unique recommendations from each category:

• mood
• cuisine
• combo

I pass these results through a serializer,
And it converts these to JSON to be passed to the front-end as a final recommendation.

As a developer,
I can use VCR to store cassettes of API requests,
So we do not have to rely on refreshing a token that expires every hour.

All cuisine & mood types should be mapped to a param that is used in the API endpoint for those requests.

This will ensure the largest number of relevant results.

As a developer,
I can establish a connection to the Spotify API.

As a developer,
When invalid params are entered into a request,
We are handling the sad path in a way that 'fails gracefully' for the user.