The use of a Skeleton Layout for asynchronous content is becoming more and more popular across mobile and web apps alike. Google, Facebook, LinkedI...
For further actions, you may consider blocking this person and/or reporting abuse
Great article! One tip tho - ditch the loading boolean state. There is more than loading/done states. Best approach is to have idle/loading/success/error states. More management is required but, it saves users from waiting despite API call has failed.
This article by Kent is great explanation why:
kentcdodds.com/blog/stop-using-isl...
ahah, I was about to post this, well played.
Actually, his (Kent's) initial structure is not that bad, in his specific case all he needed to do is a) clear position on error or b) move error check higher that position check, i.e. ensuring error's priority
Great tip, I will look into this article! Thanks a ton!!!
I wish people would stop quoting Kent C Dodds.
Why is that?
Great write up. I always wondered how these guys did it but this article really gave me a head start 😊
Awesome sauce! You should be using functional components. Class based components are no longer recommended.
Thanks James, I was thinking that when building the example but wanted to keep this code tutorial accessible to users that may have not made that switch. I might consider transitioning the codepen in the near future.
Great
Nice 👍