482e3fbffa
Similar to #40872 `useSearchParams` now returns a `URLSearchParams` instance instead of a plain object. ## 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)
13 lines
568 B
TypeScript
13 lines
568 B
TypeScript
import { createContext } from 'react'
|
|
|
|
export const SearchParamsContext = createContext<URLSearchParams>(null as any)
|
|
export const PathnameContext = createContext<string>(null as any)
|
|
export const ParamsContext = createContext(null as any)
|
|
export const LayoutSegmentsContext = createContext(null as any)
|
|
|
|
if (process.env.NODE_ENV !== 'production') {
|
|
SearchParamsContext.displayName = 'SearchParamsContext'
|
|
PathnameContext.displayName = 'PathnameContext'
|
|
ParamsContext.displayName = 'ParamsContext'
|
|
LayoutSegmentsContext.displayName = 'LayoutSegmentsContext'
|
|
}
|