fix: HOTFIX useHistory currentIndex more than MAX_HISTORY_LENGTH cause replace fail #8819
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When add input history more than MAX_HISTORY_LENGTH, cause
pre()fail, becausecurrentIndex = MAX_HISTORY_LENGTH + 1:AI Code Review
@continue-reviewChecklist
Screen recording or screenshot
[ When applicable, please include a short screen recording or screenshot - this makes it much easier for us as contributors to review and understand your changes. See this PR as a good example. ]
Tests
Small fix without unit test.
Summary by cubic
Limit currentIndex to MAX_HISTORY_LENGTH to prevent history navigation from breaking when the list exceeds the cap.
Written for commit ff480a3. Summary will update automatically on new commits.