Open laurencmendoza opened 1 year ago
Great work on this return statement! Modularity is good here, but I wonder if the details page could handle the playlist name, image, and audio analysis as well? Perhaps when all the data finally comes back (I'm assuming there are multiple fetch requests), then the one loading animation will disappear! Just a thought, but would probably involve quite the refactor. Keep us posted!
what is one area in your code that can be improved or what is already great, but could be enhanced? Why?
This is the return statement for my playlist details page, which has the playlist tracks component, which then has the audio analysis component for each track. Separating the three components allowed me to render each track's audio analysis on one page and allowed me to separate code for the different components of the page, but as of now, my loading animation only plays while the playlist name and image are loading at the top of the page, and there is a separate loading animation for the audio analysis for each track. Ideally, I'd like one loading animation for the whole page, while all of the information is getting pulled from the API, including the audio analysis. I tried finding a way to refactor it, but I was unsuccessful so far.