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.
Autocomplete is changing the uncontrolled value state to be controlled.
See original GitHub issueDescribe the bug Autocomplete is changing the uncontrolled value state to be controlled when choosing option
To Reproduce Steps to reproduce the behavior:
- Go to codesandbox
- Try choose any option
- See console.
Expected behavior Shouldn’t change state
I think this is due to the fact that the defaultValue remains undefined if getOption was passed but value was not.
Maybe set to null by default, because from react-final-form:
By default, if your value is null, <Field/> will convert it to ‘’, to ensure controlled inputs
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:22 (12 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
@Lucas-Alf Thanks for the update. I’ve reopened for now until myself or someone else can find the time to investigate this further.
I had a similar problem trying to create a Autocomplete component with server side data fetch. Try to remove this line and see if stops giving that error: https://github.com/lookfirst/mui-rff/blob/646a5393705093508fad8acedecbdda11584d0b7/src/Autocomplete.tsx#L150
Looks like is something with the defaultValue equals to undefined. For my custom component i just removed this line and the problem is gone, i really don’t need the defaultValue in my use case.
If someones wants see my component (not TS): https://github.com/Lucas-Alf/resoar/blob/main/src/components/AutocompleteServerSide/AutocompleteAdapter.jsx