From 22087452cd54e0132ae0c9d0027ccf3a03fddda9 Mon Sep 17 00:00:00 2001 From: JJ Kasper Date: Sun, 24 Apr 2022 21:27:13 -0500 Subject: [PATCH] Revert "Change getStaticProps to getStaticPaths in getStaticPaths docs (#36403)" This reverts commit 2a42de2fd18a7c06a8f3d931405386a8283280ef. --- docs/basic-features/data-fetching/get-static-paths.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/basic-features/data-fetching/get-static-paths.md b/docs/basic-features/data-fetching/get-static-paths.md index 3865dea07828..a5fa8d9c7453 100644 --- a/docs/basic-features/data-fetching/get-static-paths.md +++ b/docs/basic-features/data-fetching/get-static-paths.md @@ -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` runs during `next build` for any `paths` returned during build -- `getStaticPaths` runs in the background when using `fallback: true` -- `getStaticPaths` is called before initial render when using `fallback: blocking` +- `getStaticProps` runs during `next build` for any `paths` returned during build +- `getStaticProps` runs in the background when using `fallback: true` +- `getStaticProps` is called before initial render when using `fallback: blocking` ## Where can I use getStaticPaths