Respect PaginationHandler.handle() stop signal in ResultUtils.processClassNames#3224
Open
vasiliy-mikhailov wants to merge 1 commit into
Open
Conversation
…ClassNames PaginationHandler.handle() documents its boolean return as: true keep processing, false stop. processClassNames ignored it, so a handler returning false still received every remaining segment. Guard the in-loop call so a false return ends processing. Adds a regression test.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
ResultUtils.processClassNamesignores thebooleanreturned byPaginationHandler.handle(...). The handler's own Javadoc documents the contract:(true = keep processing the remaining data, false = stop). Because the return value is discarded, a handler that returns
falseto stop early still receives every remaining segment.This guards the in-loop call so that a
falsereturn ends processing. Adds a regression test (ResultUtilsTest.testHandleReturnFalseStopsProcessing) that fails before the change — the handler returningfalseis still invoked for all 3 segments (expected:<1> but was:<3>) — and passes after.AI assistance disclosure
This contribution was produced with the help of an AI pipeline. The pipeline processed a large amount of source code to surface suspected bugs, reproduced a subset of them with failing unit tests and generated candidate fixes, and prepared pull requests from the ones that held up. Each PR was then reviewed and verified by a human before being opened: the fix and test were checked by hand and the test was confirmed to fail before the change and pass after.