Unverified Commit 2a42de2f authored by youngvform's avatar youngvform Committed by GitHub

Change getStaticProps to getStaticPaths in getStaticPaths docs (#36403)

## Overview
The subject is `When does getStaticPaths run` but this docs denotes about `getStaticProps`.
So could you check `getStaticProps` is right?

## Documentation / Examples

- [X] Make sure the linting passes by running `yarn lint`
parent ec4f96c9
...@@ -37,9 +37,9 @@ You should use `getStaticPaths` if you’re statically pre-rendering pages that ...@@ -37,9 +37,9 @@ You should use `getStaticPaths` if you’re statically pre-rendering pages that
`getStaticPaths` will only run during build in production, it will not be called during runtime. You can validate code written inside `getStaticPaths` is removed from the client-side bundle [with this tool](https://next-code-elimination.vercel.app/). `getStaticPaths` will only run during build in production, it will not be called during runtime. You can validate code written inside `getStaticPaths` is removed from the client-side bundle [with this tool](https://next-code-elimination.vercel.app/).
- `getStaticProps` runs during `next build` for any `paths` returned during build - `getStaticPaths` runs during `next build` for any `paths` returned during build
- `getStaticProps` runs in the background when using `fallback: true` - `getStaticPaths` runs in the background when using `fallback: true`
- `getStaticProps` is called before initial render when using `fallback: blocking` - `getStaticPaths` is called before initial render when using `fallback: blocking`
## Where can I use getStaticPaths ## Where can I use getStaticPaths
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment