Skip to content

Commit 84fa36e

Browse files
authored
docs: Update create-browser-router.md (#11595)
* Update create-browser-router.md * Sign CLA
1 parent 0999f6f commit 84fa36e

File tree

2 files changed

+2
-1
lines changed

2 files changed

+2
-1
lines changed

contributors.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,7 @@
8282
- frontsideair
8383
- fyzhu
8484
- fz6m
85+
- gesposito
8586
- gianlucca
8687
- gijo-varghese
8788
- goldins

docs/routers/create-browser-router.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -339,7 +339,7 @@ let router = createBrowserRouter(routes, {
339339
It's also possible you don't even want to define a loader implementation at the route level. Maybe you want to just determine the routes and issue a single GraphQL request for all of your data? You can do that by setting your `route.loader=true` so it qualifies as "having a loader", and then store GQL fragments on `route.handle`:
340340

341341
```ts
342-
const routes [
342+
const routes = [
343343
{
344344
id: "parent",
345345
path: "/parent",

0 commit comments

Comments
 (0)