Fix nested JSON parameter normalization#25
Merged
Conversation
adsharma
force-pushed
the
fix/nested-json-parameters
branch
from
d9aff9c to
00d4371
Compare
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.
Summary
Fix
to_json($param)handling for Python JSON parameters that contain mixed scalar and nested values in the same list.Root Cause
The JSON parameter normalization path only forced JSON serialization for empty or otherwise unresolved nested shapes. Lists like
["entry1", "entry2", {"key": "value"}]were treated as typed parameters even though their mixed scalar/object structure is a JSON shape.Changes
@contextJSON data.Validation
uv run pytest test/test_json.py test/test_parameter.py test/test_issue.py::test_issue_483_numpy_ndarray_parameter -quvx ruff check src_py/connection.py test/test_json.py