appbaseio / appbaseio/reactivesearch
[ERROR] DateRange: Maximum update depth exceeded
- Dominant language
- JavaScript
- Stars
- 4.9k
- Forks
- 478
- PR merge metrics
- No merged PRs in 30d
Description
**Affected Projects**
Reactivesearch
**Library Version:**
4.2.0
**Describe the bug**
Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to the demo link mentioned in the docs - https://codesandbox.io/s/github/appbaseio/reactivesearch/tree/next/packages/web/examples/DateRange?from-embed=&file=/src/index.js
2. Try selecting any start/end date with DateRange component
**Expected behavior**
Expect the results cards to be filtered out based on date range provided
**Screenshots**

**Video**
https://github.com/appbaseio/reactivesearch/assets/85502721/55d20215-07ac-4223-a147-f57686137ddd
**Desktop (please complete the following information):**
- OS: macOS
- Browser: Chrome
- Version: 119.0.6045.123 (Official Build) (x86_64)
**Additional context**
Have been facing a similar issue in my project where the app errors out if you select a daterange
Contributor guide
Research direction
Start by reproducing the error in the DateRange CodeSandbox linked in the issue, using the example entry point at packages/web/examples/DateRange/src/index.js. Trace the DateRange selection flow and verify that choosing start and end dates filters the result cards without triggering the maximum update depth error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100