Skip to content

Commit e310d11

Browse files
authored
[docs] fix generated types link fragment (#5229)
1 parent 733bd2f commit e310d11

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

documentation/docs/04-loading.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ If the data for a page comes from its endpoint, you may not need a `load` functi
2626

2727
> Note the `<script context="module">` — this is necessary because `load` runs before the component is rendered. Code that is per-component instance should go into a second `<script>` tag.
2828
29-
As with [endpoints](/docs/routing#endpoints), pages can import [generated types](/docs/types#generated) — the `./[slug]` in the example above — to ensure that `params` are correctly typed.
29+
As with [endpoints](/docs/routing#endpoints), pages can import [generated types](/docs/types#generated-types) — the `./[slug]` in the example above — to ensure that `params` are correctly typed.
3030

3131
`load` is similar to `getStaticProps` or `getServerSideProps` in Next.js, except that `load` runs on both the server and the client. In the example above, if a user clicks on a link to this page the data will be fetched from `cms.example.com` without going via our server.
3232

0 commit comments

Comments
 (0)