Next Twitter update will remember whether you were on For You (ie recommended), Following or list you made & stop switching you back to recommended tweets
@npmjs there are multiple discussions on your community discussions sharing similar sentiment to @_developit and the answer I got from your support is that they have no way to grant exemptions. Can you please address this.
https://t.co/1vetP5u6Yr
https://t.co/GK9ys7Hskw
@npmjs@_developit Seems like the link didn't include the search term like I intended. Here is a new link. If you are having this issue yourself please upvote.
https://t.co/lyAaL7G4qU
React Compiler: Rust edition is coming soon. We've ported the majority of the passes using AI. When the initial port finishes we'll do some updates to get the code in a state we're happy to maintain, then extensive testing and look at performance. More to come soon
@RyanCarniato@VictorTaelin is using AI for research. Maybe you should check out his posts about the topic? I think what models to use and how to prompt differ greatly between general coding and research.
@ryanflorence I think this issue is similar to the problem Remix is trying to solve with the AbortAignals in events however this signal would somehow have to be tied to document.activeElement. There should ever only be one task scheduled to update activeElement.
@ryanflorence How would this work if the submit is async? While waiting for it to complete I might move focus and start working on something else. I would no longer expect the focus move on completion of submit to happen as that would rip focus away from the new thing I'm working on.
@RyanCarniato@fabiospampinato SSR don't really work with local first apps. You can't server render based on the browsers local storage. Sure you can SSR some shell but at that point you are mostly just building an SPA anyway.
@rickyfm@RyanCarniato Yes it does but I'm not sure what it really changes over mine. My version already did what i want.
I was asking if adding optimistic to the form like that is the intended way to opt out of the design components built in pending state.
@rickyfm@RyanCarniato Think you misunderstood what i asked or something. Might have golfed my tweet too much 😅. Was basically just asking if moving the loading state using optimistic in that way is a reasonable way to solve this kind of problem in "Async React™" or if you have a better way.
@rickyfm@RyanCarniato Kind of hard to make this work with default values. What do you think of this solution? The form uses optimistic it self to move the loading state to the other select. https://t.co/aTRsw66zuK
@rickyfm@RyanCarniato Or maybe not. All async stuff being in a the inner Suspense boundary causes the transition to end early not showing the loading state on the first select. 🤯
@rickyfm@RyanCarniato Shouldn't design components generally show a loading state when isPending is true or value !== optimisitcValue. If your Select did that you would get loading state on both selects in your demo. How would you let the design component user control what select shows loading?
@RyanCarniato Just a hack to get the use to be treated as something inside the Suspense boundary. The linter might yell at me in a real code base so I should probably refactor. I was more focused on how the code using Select would look than its implementation.