Fix Create, Edit and Show cannot be used outside of a ResourceContextProvider

[fzaninotto]

Closes #5662

Although the <Create>, <Edit> and <Show> components were never meant to be used outside of <Resource> props, developers have taken the habit to use them in standalone, passing the resource as prop. The fact that it worked was undocumented, but intuitive and practical.

The introduction of the <ResourceContextProvider> broke this. An attempt to use <Create resource="foos"> fails - the user has to wrap the component in a <ResourceContextProvider>.

We recognize that <Create>, <Edit> and <Show> should be usable outside of <Resource>, so they should be able to create their own <ResourceContextProvider> when passed a resource prop.

[fzaninotto]

I'v considered extracting this duplicated logic to a dedicated component, like so:

const ConditionalWrapper = ({ condition, wrapper, children }) => 
  condition ? wrapper(children) : children;

...

<ConditionalWrapper
   condition={props.resource}
   wrapper={children => <ResourceContextProvider value={props.resource}>{children}</ResourceContextProvider>}
>
    <CreateContextProvider value={controllerProps}>
        <CreateView {...props} {...controllerProps} />
    </CreateContextProvider>
</ConditionalWrapper>

But I find it less legible. Besides, the duplication is only a few lines.

[fzaninotto]

rebased

[koaladlt]

Do we have any updates on this? Is there a way to use Create with a different endpoint?

[fzaninotto]

@koaladlt The updates on this PR is that it's merged and published in 3.11, as the "Milestone" zone on the right column suggests.

About your other question, please consider asking it on stackOverflow. As explained in the issue template, we don't do free support on gitHub issues.