docs(guides/deferred): add FAQ about using Response objects with defer
#10000
Conversation
After explaining how React Router uses response objects to replicate web standard behavior, it can be confusing why this suddenly stops working just by adding "defer" to the loader's return value. Thinking it through yields the answer (deferred data isn't handled by the response returning the HTML), but it seems like it would reduce the friction to add a little explanation.
|
|
Hi @landisdesign, Welcome, and thank you for contributing to React Router! Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once. You may review the CLA and sign it by adding your name to contributors.yml. Once the CLA is signed, the If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at hello@remix.run. Thanks! - The Remix team |
|
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
MichaelDeBoey
changed the title
Response objects with defer
|
Thanks! This type of question has come up before too where folks forget to call |
|
I like the change! I appreciate how it goes into making the loader more responsive to deferred responses. I think this could still benefit from a code example for the component, to illustrate how it now needs to manage the redirect rather than leaving it to the loader. I know that's what tripped me up. |
3 participants
After explaining how React Router uses response objects to replicate web standard behavior, it can be confusing why this suddenly stops working just by adding "defer" to the loader's return value. Thinking it through yields the answer (deferred data isn't handled by the response returning the HTML), but it seems like it would reduce the friction to add a little explanation.