355bd12c61
As of [React 19](https://react.dev/blog/2024/12/05/react-19), context providers no longer require the `<MyContext.Provider>` syntax and can be rendered as `<MyContext>` directly. This will be deprecated in future versions of React, which is now being caught by the [`@eslint-react/no-context-provider`](https://eslint-react.xyz/docs/rules/no-context-provider) ESLint rule. Similarly, the [`use`](https://react.dev/reference/react/use) API is now preferred over `useContext` because it is more flexible, for example they can be called within loops and conditional statements. See the [`@eslint-react/no-use-context`](https://eslint-react.xyz/docs/rules/no-use-context) ESLint rule for more details.
14 lines
449 B
TypeScript
14 lines
449 B
TypeScript
'use client'
|
|
import React, { createContext, use } from 'react'
|
|
|
|
export const OperationContext = createContext('' as Operation)
|
|
|
|
export const OperationProvider: React.FC<{ children: React.ReactNode; operation: Operation }> = ({
|
|
children,
|
|
operation,
|
|
}) => <OperationContext value={operation}>{children}</OperationContext>
|
|
|
|
export type Operation = 'create' | 'update'
|
|
|
|
export const useOperation = (): Operation | undefined => use(OperationContext)
|