Unverified Commit e8320075 authored by JJ Kasper's avatar JJ Kasper Committed by GitHub

Revert "Change getStaticProps to getStaticPaths in getStaticPaths docs" (#36425)

This change was un-necessary and `getStaticProps` was correct here so this reverts the change. 

Reverts vercel/next.js#36403
parent a0b70067
...@@ -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/).
- `getStaticPaths` runs during `next build` for any `paths` returned during build - `getStaticProps` runs during `next build` for any `paths` returned during build
- `getStaticPaths` runs in the background when using `fallback: true` - `getStaticProps` runs in the background when using `fallback: true`
- `getStaticPaths` is called before initial render when using `fallback: blocking` - `getStaticProps` 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