NW | Data flows | Ahmad Hmedan

[AhmadHmedann]

Codewars Evidence
https://codeyourfuture.github.io/Codewars-Progress-Checker/#AhmadHmedann
Netlify
https://cyf-ahmadhmedann-tv.netlify.app/
https://github.com/AhmadHmedann/Project-TV-Show
level 400 PR
jakr-s/Project-TV-Show#5
Level 200 PR
jakr-s/Project-TV-Show#1
level 500 PR
AhmadHmedann/Project-TV-Show#2
Book Library Project
CodeYourFuture/Module-Data-Flows#360
LinkedIn Social Selling Index
#50

[cjyuan]

The following TV Show requirement has not yet been met:

• During one user's visit to your website, you should never fetch any URL more than once. (levels 300, 400, 500)
• Add a select element to your page so the user can choose a show. (level 400)
  • Note: This select element is similar to the one you have for episodes. You just need to add one for all shows on the show listing page.

[AhmadHmedann]

Thanks for the feedback
I already had this function implemented earlier, and I thought it wasn’t needed for Level 500. For the fetch logic

is that dose not work??
if (state.episodeByShowId.has(showId)) {
episodes = state.episodeByShowId.get(showId);
} else {
episodes = await fetchEpisodesForShow(showId);
state.episodeByShowId.set(showId, episodes);
}
I'm using caching, when the user click on a show,. I check if the episodes already exist in state.episodeByShowId, if true I do not request a fetch
if false I fetch the episodes once and store them in the state.episodeByShowId
and I test it in Dev-tool

[cjyuan]

Sorry I overlooked the caching part -- I only checked out the fetch functions and expected the caching mechanism to be built into them.

The app meets all the requirements now.

[AhmadHmedann]

No worries at all. I appreciate the feedback. It really helps me improve my skills and gain a better understanding of how things should be structured. Thanks for taking the time to review it