docs: fix ScrollRestoration getKey example (#9266)

Co-authored-by: Tim Dorr <timdorr@users.noreply.github.com>
remix-run · Sep 15, 2022 · 30c1b5c · 30c1b5c
1 parent 7520e78
commit 30c1b5c
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 3 deletions.
diff --git a/contributors.yml b/contributors.yml
@@ -105,3 +105,4 @@
 - xavier-lc
 - xcsnowcity
 - yuleicul
+- GraxMonzo
diff --git a/docs/components/scroll-restoration.md b/docs/components/scroll-restoration.md
@@ -28,7 +28,7 @@ Optional prop that defines the key React Router should use to restore scroll pos
 
 ```tsx
 <ScrollRestoration
-  getKey={({ location, matches }) => {
+  getKey={(location, matches) => {
     // default behavior
     return location.key;
   }}
@@ -58,7 +58,7 @@ A solid product decision here is to keep the users scroll position on the home f
 
 ```tsx
 <ScrollRestoration
-  getKey={({ location, matches }) => {
+  getKey={(location, matches) => {
     return location.pathname;
   }}
 />
@@ -68,7 +68,7 @@ Or you may want to only use the pathname for some paths, and use the normal beha
 
 ```tsx
 <ScrollRestoration
-  getKey={({ location, matches }) => {
+  getKey={(location, matches) => {
     const paths = ["/home", "/notifications"];
     return paths.includes(location.pathname)
       ? // home and notifications restore by pathname