Data source: swyx's twitter data
| id | user | created_at | full_text | retweeted_status | quoted_status | place | source | truncated | display_text_range | in_reply_to_status_id | in_reply_to_user_id | in_reply_to_screen_name | geo | coordinates | contributors | is_quote_status | retweet_count | favorite_count | favorited | retweeted | possibly_sensitive | lang | scopes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1457535446674718725 | 727704217012604928 | 2021-11-08T02:28:24+00:00 | I spent the afternoon hacking on the experimental RTK "action listener middleware" API. After applying multiple suggestions, I'm excited to report that: **it now has support for long-running async workflows!** Changelog, discussion, and "docs" here: https://github.com/reduxjs/redux-toolkit/discussions/1648#discussioncomment-1603347 | 9335de48b3673c3f69433a34861c115d1d382be3 | 0 | [0, 277] | 0 | 2 | 32 | 1 | 1 | 0 | en | ||||||||||
| 1458630426709442562 | 727704217012604928 | 2021-11-11T02:59:28+00:00 | In the spirit of "working in public", but also "I'm human" and "ARGH THIS IS BROKEN SOMEONE HELP ME": I've spent the last few days trying to rewrite the new RTK middleware types. Thus far I have completely failed. The _horribly_ hacked-up code is here: https://github.com/reduxjs/redux-toolkit/commits/feature/listener-middleware-fixes | 9335de48b3673c3f69433a34861c115d1d382be3 | 0 | [0, 280] | 0 | 2 | 20 | 1 | 1 | 0 | en |