Jacob Fletcher
355bd12c61
chore: infer React context providers and prefer use ( #11669 )
...
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.
2025-03-12 15:48:20 -04:00
Jacob Fletcher
f5683b0a64
fix(next): threads server props to custom providers ( #9412 )
...
When defining custom providers as server components, they currently do
not receive any of the server props that custom components expect to
receive, like `payload`, `i18n`, `user`, and so on.
2024-11-21 15:44:32 -05:00
Alessio Gravili
847a2994f9
chore: work on e2e's
2024-03-08 12:33:44 -05:00
Jarrod Flesch
5de7d7f882
chore: test improvements and fixes
2024-03-04 14:24:28 -05:00
James
0f3b364e46
chore: hoists tests out of payload package
2023-09-01 14:45:41 -04:00
Alessio Gravili
a67278b29f
chore: move to monorepo structure
2023-08-23 12:20:30 +02:00
Dan Ribbens
4c68f64829
docs: update demo links and add examples to test dir ( #773 )
2022-07-19 14:42:14 -04:00
