Add backward-compatible JSON field parsing to asset and sensor methods #165
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.
The FlexMeasures API returns JSON-encoded fields (
attributes,flex_context,flex_model) as strings. Methods likeget_assets(),get_asset(),get_sensor(), andget_sensors()previously returned these as-is, requiring manual parsing by callers.Changes
New parameter
parse_json_fields(default:None)None(default): Returns JSON strings with deprecation warningTrue: Parses JSON strings into Python dictsFalse: Returns JSON strings without warningExample usage:
Implementation details:
_parse_json_field(),_parse_asset_json_fields(),_parse_sensor_json_fields()get_asset()call in scheduler code to use parsed fieldsAffected fields:
attributes,flex_context,flex_modelattributes✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.