Share this page!

Tanner Linsley ⚛️ Profile picture
Twitter logo
5 Jan, 3 tweets, 2 min read
#ReactQuery and #ReactTable's sponsors sections are now automatically generated from the Github GQL API + Airtable (for customizations and non-GH sponsors).

It uses @Airbnb's visx library to circle pack, but with divs instead of svg 😂

No more manually updating sponsors! 🎉
@Airbnb Also, none of this would have been easy without @vercel and @airtable
Ah, looks like I accidentally featured @kentcdodds as the hovered/tooltip'd sponsor. Thanks Kent!

• • •

Missing some Tweet in this thread? You can try to force a refresh
　

Keep Current with Tanner Linsley ⚛️

Tanner Linsley ⚛️ Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @tannerlinsley

Tanner Linsley ⚛️ Profile picture
15 Jul 20
@theefer @OliverJAsh I’ll respond more at my keyboard, but the simple solution to this is to adopt invalidation patterns over manual data normalization. Just invalidate all of the queries. They already know how to fetch the exact data they need.
@theefer @OliverJAsh Regardless of React Query or not, normalized caches on the front-end come with the upside of fetching less data and using the responses of mutations as much as possible. When you like a tweet, you just go find that tweet in your store and update it

...
@theefer @OliverJAsh This situation works fine if that action doesn't have any side effects on the rest of the system. Imagine tweet deck that is showing only liked tweets, or a list that is sorted by time of liking. This now means that you either have to replicate all of the logic on your server

..
Read 11 tweets
Tanner Linsley ⚛️ Profile picture
9 Jul 20
Lots of talk about React suspense today. I’m very excited about it.

However, I feel like the patterns I’ve seen in #ReactQuery (and friends like SWR) have alone been more transformative for my own dev process and users and have even prepped me for suspense in a lot of ways.
Of course, Suspense isn’t out yet, and the ecosystem will likely experience a smash of collective inovation around it when it comes out. That’s the exciting part. But what I feel like I’m starting to realize after playing around with it is that in the end,
The biggest thing that suspense is going to do for me is just one thing: avoiding that flash of loading/placeholder for newly mounted components. Suspense doesn’t fetch, it doesn’t codesplit, it doesn’t preload for you and it doesn’t cache for you.
Read 11 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

Like this author's thread?

Get emails when @tannerlinsley has new unrolls!

Check out other threads from @tannerlinsley!

Read all threads by @tannerlinsley