Repository navigation
[v2] pagination: Return error on missing resource key - #3976
Merged
Merged
Conversation
This doesn't appear to have ever been used. Signed-off-by: Stephen Finucane <[email protected]>
This is better than silently failing. Signed-off-by: Stephen Finucane <[email protected]> Assisted-By: Claude Opus 4.6 <[email protected]>
github-actions
Bot
added
v2
mandre
approved these changes
Aug 20, 2026
|
coverage: 63.94% (+0.005%) from 63.935% — bp-v2-00acdae-e0ba184 into v2 |
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
4 participants
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.
Backport: #3975
A follow-up to #3947 that returns an error if the requested key was not found on a page, rather than silently ignoring the key.