Loading Skeleton for Search & Pagination in NextJs 13 Movie App 

My pleasure!

Glad to hear that! Appreciate your comment.

You're welcome. I'm glad to hear that.

Glad it was helpful! Welcome to the channel.

Great suggestion! Glad you found it helpful.

Glad you liked it!

You're welcome 😊

Thanks 🔥

You're welcome! That's right it won't effect the fetch deduplication, and it won't disable the client cache entirely either, it just re-renders the component with the key prop.

Thank you so much Hamed, that was really hard to discover it to me :D !@@hamedbahram

That might me an interesting and unnecessary thing but , is there any chance like to deploy next project to vercel with the server cache we got in local ? :D@@hamedbahram

Interesting scenario here 🤔 I'd have to see the code for this to know how you're implementing all these requests. Use the key and let me know how it goes.

Key attribute doesn't seem to work

@@hey............. If you turn the whole page or all your fetch requests to dynamic, does it solve the problem?

Yes, definitely

What this video for handing errors → ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-uAh6ZOytUDk.html

Yes the `Image` component allows you to show a blurred placeholder before the actual image loads. You can read more here → nextjs.org/docs/app/api-reference/components/image#placeholder

@@hamedbahram Hey, thanks for all the hard work you put into this channel, I learned a lot from you. I have another question, instead of passing in a random key, what if we pass in the search param as key so that repeated searches will hit the cache. I am just thinking out loud and haven't tried to implement it. What do you think? BTW the way you solved it in the first place really showed your knowledge of how things work behind the scene, I would never thought of a workaround like that. Very impressive.

@@liu-river Glad to hear you've learned from my channel. That's an interesting idea 🤔try it out and let me know how it goes.

@@hamedbahram I watched your video again just to consolidate what is happening here. I used the Await helper which is super cool BTW to use in conjunction with Suspense. My theory worked. My app is a filter rather than a search but the logic is the same right, so on searchParams thats already been visited, no waiting, cache hit and page render straightaway. On the other hand searchParams that have not been cached, loading UI kicks in. It's so smooth. I passed key={searchParams.sort as string} to my top div rather than UUID. Thanks again Hamed!

Suspense fallback only shows the first time.

Not sure why you're experiencing that. It works on my end => next-pagination-one.vercel.app/

is the problem with nginx?

@@deepanshuverma3536 Not sure!

I'm not sure if I understand the question!

Why would that be?

Merc, hatman!