FlexMeasures / flexmeasures / 29949045536

83%

push

github

Show inherited flex-context fields in the flex-context editor (#2346)

* feat: show the resolved flex-context on the asset context page

Scheduling an asset resolves its flex-context by filling in missing
fields from ancestors, which made it hard to see in the UI which values
a schedule would actually use. The context page now shows the resulting
flex-context, saying for each field whether it is set on the asset
itself or inherited, with a link to the defining ancestor.

The merge logic in get_flex_context is refactored to track each field's
origin (get_flex_context_with_provenance), keeping a single source of
truth for the resolution order. Saving the flex-context editor now
reloads the page, so the table reflects the saved changes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015qxM7UZ5wHTz3ftz1Mf9yy
Signed-off-by: F.N. Claessen <felix@seita.nl>

* test: cover flex-context provenance and its display on the context page

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015qxM7UZ5wHTz3ftz1Mf9yy
Signed-off-by: F.N. Claessen <felix@seita.nl>

* docs: changelog entry for the resolved flex-context view

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015qxM7UZ5wHTz3ftz1Mf9yy
Signed-off-by: F.N. Claessen <felix@seita.nl>

* feat: refresh the resolved flex-context in place, and link sensor references

Saving the flex-context editor no longer reloads the page: the table is
extracted into a fragment template, served by a new
/assets/<id>/context/resolved-flex-context endpoint, which the page
fetches after a successful save. Sensor references in field values now
render as links to the sensor pages, labeled with the sensor's name,
for sensors the user is allowed to read.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015qxM7UZ5wHTz3ftz1Mf9yy
Si... (continued)

11 of 11 new or added lines in 2 files covered. (100.0%)

15814 of 19102 relevant lines covered (82.79%)

0.83 hits per line