fix: normalize job metadata JSON string to dict in job reponses#52
Merged
MatehElismar merged 1 commit intomasterfrom Mar 19, 2026
Merged
Conversation
The API returns job metadata as a JSON-encoded string. This adds normalization in Jobs.get and Jobs.get_all so metadata is always a dict by the time it reaches the caller. Relates to: TAG-2271
rroa
approved these changes
Mar 19, 2026
mlovera
approved these changes
Mar 19, 2026
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.
Issue/Ticket: TAG-2273
Summary
When fetching jobs, the API returns the
metadatafield as a JSON-encoded string rather than a parsed object. This caused callers to receive raw strings instead of usable dicts, leading to mismatches in processing and downstream consumption. This fix adds normalization in the SDK so thatmetadatais always a dict by the time it reaches the caller.Changes
Jobs.getandJobs.get_allnow parse JSON-string metadata into a dict before returningresultkey with single job or list), direct job objects, and edge cases (empty, invalid JSON, non-dict values — all coerced to{})tests/test_smoke.pywith unit tests covering the normalization scenariostest.py(replaced by proper test structure); updatedMakefileto usepython -m unittest