a92a3b6d3a
Since React 18 returning `undefined` from components is allowed which renders to `undefined` in the RSC response so we need a separate prop to know if the loading boundary was provided. Thanks to @finn-orsini who reported this problem. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) |
||
---|---|---|
.. | ||
shared/dynamic | ||
app-router.client.tsx | ||
hooks-client-context.ts | ||
hooks-client.ts | ||
hooks-server-context.ts | ||
hooks-server.ts | ||
hot-reloader.client.tsx | ||
infinite-promise.ts | ||
layout-router.client.tsx | ||
match-segments.ts | ||
not-found.ts | ||
redirect.ts | ||
reducer.ts | ||
render-from-template-context.client.tsx | ||
request-async-storage.ts | ||
static-generation-async-storage.ts | ||
use-reducer-with-devtools.ts |