-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove injected props in Admin and Layout components #9591
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## Problem The Layout component is the last one requiring props cloning in user land: ```jsx // in src/MyLayout.js import { Layout } from 'react-admin'; import { MyAppBar } from './MyAppBar'; export const MyLayout = props => ( <Layout {...props} appBar={MyAppBar} /> ); ``` Developers wonder: what is props? Why do I have to pass it down? It’s not so usual in modern React. ## Solution Use a context instead, and just pass the children down (which requires no explaining). ```jsx // in src/MyLayout.js import { Layout } from 'react-admin'; import { MyAppBar } from './MyAppBar'; export const MyLayout = ({ children }) => ( <Layout appBar={MyAppBar}> {children} </Layout> ); ```
fzaninotto
changed the title
Update Layout to require only children prop
Remove injected props in Admin and Layout components
Jan 22, 2024
djhi
requested changes
Jan 23, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Gildas Garcia <1122076+djhi@users.noreply.github.com>
djhi
approved these changes
Jan 24, 2024
adguernier
approved these changes
Jan 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problems
In order to build a custom layout for
<Admin layout>
, developers must clone props:Developers wonder: what is
props
? What's its type? Why do I have to pass it down? It’s not so usual in modern React.The same happens for other components that can be set on
<Layout>
:appBar
,menu
,error
,catchAll
.Solution
The only useful data injected is
title
anddashboard
. The rest is useless as the data can be obtained in another way.Use a context instead of props injection for these values. That way, a custom layout just needs to pass the children down (which requires no explaining).
Also, remove deprecated prop injection as there are alternatives.
Tasks
layout
menu
appBar
error
catchAll