Refactor: Implement Reusable Loading Screen Logic about wanderlust HOT 4 OPEN

Thanks for asking @krishnaacharyaa, please assign it to me :)

from wanderlust.

Thank you @hemant14050 for creating the issue, please let us know if you are interested, we'll assign it to you :)

from wanderlust.

@hemant14050 I'd like to ask you for some more clarification on this:

Tell me if I understand this correctly:
You are proposing to dynamically show which posts are fetched from the collections and if the post is fetched, a bool will set loading to false for that specific post?

Let's say I have 10 posts, and I just refreshed the page, and it takes 10 seconds to completely load my page.
So, after your implementation, will it look like this?

0th second (nothing is fetched yet):
Skeleton
Skeleton
Skeleton
Skeleton
Skeleton
Skeleton
Skeleton
Skeleton
Skeleton
Skeleton

2nd second (2nd and 7th post is fetched):
Skeleton
Post visible
Skeleton
Skeleton
Skeleton
Skeleton
Post Visible
Skeleton
Skeleton
Skeleton

5th second (4 posts fetched):
Skeleton
Post visible
Skeleton
Post Visible
Skeleton
Skeleton
Post Visible
Post Visible
Skeleton
Skeleton

10th second (all posts fetched):
Post Visible
Post Visible
Post Visible
Post Visible
Post Visible
Post Visible
Post Visible
Post Visible
Post Visible
Post Visible

Thanks.

from wanderlust.

This is interesting @chinmaykunkikar, but presently this happens because of the image rendering, but not sure if this parallel fetching of post is even possible, happy to know the approach though,

But the whole idea was to just refactor the code, No changes with respect to the visual appearance in the application. Focusing on DX mostly than UX here.

from wanderlust.