Skip to content
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

Avoid cloning element for optionText #7215

Merged
merged 8 commits into from
Feb 10, 2022
Merged

Conversation

djhi
Copy link
Collaborator

@djhi djhi commented Feb 9, 2022

No description provided.

@djhi djhi added the RFR Ready For Review label Feb 9, 2022
@djhi djhi added this to the 4.0.0-alpha.3 milestone Feb 9, 2022
@djhi djhi added WIP Work In Progress and removed RFR Ready For Review labels Feb 9, 2022
@djhi djhi added RFR Ready For Review and removed WIP Work In Progress labels Feb 9, 2022
@vercel vercel bot temporarily deployed to Preview – react-admin February 9, 2022 16:10 Inactive
Co-authored-by: Aníbal Svarcas <WiXSL@users.noreply.github.com>
Co-authored-by: Aníbal Svarcas <WiXSL@users.noreply.github.com>
Copy link
Contributor

@WiXSL WiXSL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AutocompleteArrayInput.tsx also has the same JsDocs and needs to be changed.

`optionText` also accepts a React Element, that will be cloned and receive
the related choice as the `record` prop. You can use Field components there.
Note that you must also specify the `matchSuggestion` prop

@fzaninotto
Copy link
Member

Needs rebase

@vercel vercel bot temporarily deployed to Preview – react-admin February 10, 2022 15:09 Inactive
@fzaninotto fzaninotto merged commit 66197e9 into next Feb 10, 2022
@fzaninotto fzaninotto deleted the avoid-cloning-optionText branch February 10, 2022 16:11
@fzaninotto fzaninotto mentioned this pull request Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFR Ready For Review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants