You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the <Edit>, <Create> and <Show> components, the title property is typed as title?: string | ReactElement;
In our project, we would like to customize title content using the <Title> component within the aforementioned components children. It is now uncomfortable to implement as RA stacks default title and the userland defined title.
Describe the solution you'd like
I would find it very react-admin styled to allow a false value for the title property of the core display components.
It would require to update those, adding a render condition to the <Title> component - here for example
By the way, using an empty string does not do the job as there is a falsy evaluation of the string in <PageTitle>.
Describe alternatives you've considered
None
Additional context
No relevant
The text was updated successfully, but these errors were encountered:
Supporting a falsy value for <Edit title> props does add a bit of flexibility, and we'd welcome a PR for that.
That being said, <Edit> doesn't do much more than rendering the title, actions, and a Card around the page content. If you don't use the Title feature of <Edit>, I suggest you use <EditBase> instead.
Is your feature request related to a problem?
In the
<Edit>
,<Create>
and<Show>
components, the title property is typed astitle?: string | ReactElement;
In our project, we would like to customize title content using the
<Title>
component within the aforementioned components children. It is now uncomfortable to implement as RA stacks default title and the userland defined title.Describe the solution you'd like
I would find it very react-admin styled to allow a
false
value for thetitle
property of the core display components.It would require to update those, adding a render condition to the
<Title>
component - here for exampleDescribe alternatives you've considered
None
Additional context
No relevant
The text was updated successfully, but these errors were encountered: