BUG: fix to #62205 #62320
Merged
BUG: fix to #62205 #62320
+17
−1
Conversation
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
mroeschke
approved these changes
Sep 15, 2025
|
Thanks @PluvioXO |
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.
When
record_pathis empty,json_normalizetakes a fast path that builtthe result via
DataFrame(data, index=index)but skipped applyingrecord_prefix.This change applies the same prefixing logic as the non-empty
record_pathpath.record_prefixduring the empty-record_path fast pathNo API changes beyond the bug fix. Existing behavior for non-empty
record_pathis unchanged. All tests pass locally.
Super simple fix that should fix this edge case.
Fixes #62205