Repository navigation
bug: consider object format for scalar/raw data when requesting multiple pages - #74
Merged
Merged
Conversation
aschlesin
approved these changes
Nov 10, 2026
aschlesin
left a comment
Contributor
There was a problem hiding this comment.
Checked the code on my local platform! all good.
Contributor
|
Was too early with my review - only checked raw_data and now seem to run into a bug with scalarData with this version @kan-fu |
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
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.
Fix #72.
This PR fixed the bug of paginated
outputFormat="object"responses for scalar and raw data, including row counting, sample-time handling, and page concatenation.