I've also had success with drf + drf-spectacular and then using the output OpenAPI spec to generate a typescript-react client with a third-party code generator.
It mostly just works, like you said, and almost acts as a framework guardrail: if the inferred client types are comprehensive and unsurprising then the view tends to be concise; a wonky type indicates there may be something nonstandard in the view that could be fixed by cleaner framework-abiding code.
Perhaps. I can't imagine sniping at my significant other like that. We state plainly what we mean as best we can and always try to argue in good faith. This caricature of a communication breakdown is more grotesque than relatable.
This seems to be a humor piece, but it honestly just makes me sad. My only feeling is that I wish I hadn't read it. Maybe this resonates differently to someone else?
It mostly just works, like you said, and almost acts as a framework guardrail: if the inferred client types are comprehensive and unsurprising then the view tends to be concise; a wonky type indicates there may be something nonstandard in the view that could be fixed by cleaner framework-abiding code.