[FormControl] Maximum update depth exceeded
See original GitHub issueApparently, [FormControl] component supports only one [Input]. Following code throws error Maximum update depth exceeded
<FormControl>
<Input value="a" />
<Input value="" />
</FormControl>
When both [Input]s are with empty value or both are filled, everything is okay. When one is filled and other is not, error is thrown.
I’m not sure if this is bug, but if that is intentional, I guess that Docs should mention that and React.Children.only should be used.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:6 (5 by maintainers)
Top Results From Across the Web
[FormControl] Maximum update depth exceeded · Issue #12197
When both [Input]s are with empty value or both are filled, everything is okay. When one is filled and other is not, error...
Read more >Formik Warning: Maximum update depth exceeded
Error: "Warning: Maximum update depth exceeded. This can happen when a component calls setState inside useEffect, but useEffect either ...
Read more >Child component prop causes "Maximum update depth exceeded ...
I have the following two components. Brands.js is a parent component that contains the SearchField component and passes a few props to it....
Read more >× Unhandled Rejection (Error): Maximum update depth exceeded ...
Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits ...
Read more >Multipart form with React - Text, date, number, image
Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@voliva We recommend to avoid it because some states are meant to impact a single textbox, e.g. focused, filled.
Sure, I can try. Let me dive into contributing guidelines first.