rsnext/test/integration/not-found-revalidate/pages
JJ Kasper 169785253e
Fix revalidate for initial notFound: true paths (#28097)
This fixes revalidation not occurring correctly when `notFound: true` is returned during build, additional tests have been added to ensure this is working correctly for dynamic and non-dynamic pages returning `notFound: true` during build and then revalidating afterwards.  

## Bug

- [x] Related issues linked using `fixes #number`
- [x] Integration tests added
- [x] Errors have helpful link attached, see `contributing.md`

Fixes: https://github.com/vercel/next.js/issues/21453
2021-08-14 13:11:40 +00:00
..
fallback-blocking Enable handling for revalidate and notFound (#19165) 2020-11-14 07:12:47 +00:00
fallback-true Enable handling for revalidate and notFound (#19165) 2020-11-14 07:12:47 +00:00
initial-not-found Fix revalidate for initial notFound: true paths (#28097) 2021-08-14 13:11:40 +00:00
404.js Fix revalidate for initial notFound: true paths (#28097) 2021-08-14 13:11:40 +00:00