Discussed in #10155
Originally posted by af-cf June 3, 2026
Hi. I noticed that certain components have an inconsistent placement of <Provider>. Sometimes it's the root element, sometimes it's not.
Examples:
I noticed when implementing RAC I would use render prop to render a generically styled form field container component, RAC components that do not have Provider as root would (for obvious reasons) not set the context props for elements like RAC label or error that are inside of that form field container component.
For now I am relying on testing as I implement to determine whether render prop works or not and then opt for nesting the field container component instead if render doesn't work. However I imagine ideally it should be consistent across all of the components that implement a provider.
More concrete examples in comment #10155 (reply in thread)
Discussed in #10155
Originally posted by af-cf June 3, 2026
Hi. I noticed that certain components have an inconsistent placement of
<Provider>. Sometimes it's the root element, sometimes it's not.Examples:
I noticed when implementing RAC I would use
renderprop to render a generically styled form field container component, RAC components that do not haveProvideras root would (for obvious reasons) not set the context props for elements like RAC label or error that are inside of that form field container component.For now I am relying on testing as I implement to determine whether render prop works or not and then opt for nesting the field container component instead if render doesn't work. However I imagine ideally it should be consistent across all of the components that implement a provider.
More concrete examples in comment #10155 (reply in thread)