crunchystudios / crunchy-tunes Goto Github PK

Create product vision by drafting a 'Project Summary' and adding it to the PRESS-RELEASE.md (use the format outlined in the Greenfield project repo).

Basically, the container for the Search Component. If you look at the recast.ly sprint, it'll be the Nav component equivalent.

This is the parent component for our entire app.

This will be the component encapsulating the 3 different filter options. I, Kevin, am not sure if we would like to have this component be the container for the 3 separate filter components (SC, YT, Spotify), or if we would like for this component itself to be the 3 filters.

[To be explored after basic implementation]

2 functions - 1 for the GET request for all info relating to a track (e.g. thumbnail, metadata, etc.), and another for a specific track, specified, for example, by Track ID

This will be the overall container for the collection of React Search Result Tile Components

This will be the react component for each individual tile within the overall 'search results' body. It will be 'source agnostic', meaning that it doesn't matter whether the search result is SoundCloud, YouTube or Spotify. It will account for all 3 possibilities, and render accordingly.

Utilizing Promises (bluebird library) 2 functions - 1 for the GET request for all info relating to a track (e.g. thumbnail, metadata, etc.), and another for a specific track, specified, for example, by Track ID