Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ReferenceInput label uses the wrong resource for translation message
See original GitHub issueReferenceInput in react-admin@4.02 traduct field in the same way of react-admin@3.19
When editing a resource posts with the following field
<ReferenceInput source="idUser" reference="users"><AutoComplete /></ReferenceInput>
The ReferenceInput label will be traduct with the key resources.users.fields.idUser in react-admin@4, while react-admin@3.19 use resources.posts.fields.idUser
The ReferenceField use resources.posts.fields.idUser in react-admin@3.19 and react-admin@4.02
Issue Analytics
- State:
- Created a year ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I may have a good solution. The idea is to invert the control of
FieldTitle. Instead of pushing props to it, let it pull data from a context…So
SimpleForm,ArrayInput,ReferenceInput, and many other components, should create a<FieldTitlePrefixContext>. They have the means to build a value for it.Individual inputs would just pass the props they receive to
FieldTitle:label, andsource.<FieldTitle>would use theFieldTitlePrefixContextvalue to prefix thesourceit receives in case it has nolabel.This is a pretty large change, but I think it’s the right way - it’s, in fact, the continuation of what we’ve done in the 3.0 -> 4.0 migration.
And it’s backwards compatible.
Fixed by #7110