From dd323b6dec531811ce80595ac0521455b46f0bc2 Mon Sep 17 00:00:00 2001 From: Zhong Junjie Date: Tue, 12 Nov 2024 22:17:15 +0800 Subject: [PATCH] Typo fix: '?' is placed in a wrong position (#12263) * Typo fix: '?' is placed in a wrong position * Sign CLA --- contributors.yml | 1 + docs/start/overview.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/contributors.yml b/contributors.yml index b84891fa7d..c7bd8beddc 100644 --- a/contributors.yml +++ b/contributors.yml @@ -277,6 +277,7 @@ - vitekzach - vonagam - WalkAlone0325 +- whxhlgy - willemarcel - williamsdyyz - willsawyerrrr diff --git a/docs/start/overview.md b/docs/start/overview.md index 9d287fdcb1..52ade3db5e 100644 --- a/docs/start/overview.md +++ b/docs/start/overview.md @@ -622,7 +622,7 @@ Consider a search field that updates a list as the user types: ^ lose correct state ``` -Even though the query for `q?=ryan` went out later, it completed earlier. If not handled correctly, the results will briefly be the correct values for `?q=ryan` but then flip over the incorrect results for `?q=ry`. Throttling and debouncing are not enough (you can still interrupt the requests that get through). You need cancellation. +Even though the query for `?q=ryan` went out later, it completed earlier. If not handled correctly, the results will briefly be the correct values for `?q=ryan` but then flip over the incorrect results for `?q=ry`. Throttling and debouncing are not enough (you can still interrupt the requests that get through). You need cancellation. If you're using React Router's data conventions you avoid this problem completely and automatically.