dan
Right, that's essentially the same as storing it in state. It's tied to the lifetime of the component, so it can't survive across attempts to mount it for the first...
Looking at the OP examples more closely: >https://codesandbox.io/p/sandbox/react-lazy-rerender-bug-forked-q4q6ym In this original example, there's an extra re-render. That's expected behavior: 1. First we try to render parent. It suspends. We throw...
>There's not. This is a design we landed on a while back (pre-concurrent rendering). And it's worked for a while, but it sounds like we need to rework how we're...
Another case where this is particularly painful is during a `rintro`. I constantly need to double check what the pattern is (and what I've entered so far) but as soon...
More concretely, this is how I'm spending half of my time in proofs: https://github.com/user-attachments/assets/716f1e3e-8749-403f-9bbd-2a3f68a6918e If the right pane didn't constantly disappear, I'd probably do it in ten seconds.
This has been a problem for a while. Can we set up a mirror or something in the meantime?
let's try it
We’re not currently planning to support landscape for feeds themselves (at least not in short term anyway — though i haven’t seen feed apps commonly do that in general). But...
I think we should just host them ourselves and do a pass to remove any external image links from the docs. Would you mind taking a look at that? I'd...
One argument to keep cats is to avoid churning the translations.