FlexMeasures / flexmeasures / 30095297031

83%

push

github

feat(ui): edit per-commodity flex-contexts through a commodity tab bar (#2284)

* refactor(ui): drive flex-context field types from UI_FLEX_CONTEXT_SCHEMA

Add a 'types' key to every UI_FLEX_CONTEXT_SCHEMA entry (same convention
as UI_FLEX_MODEL_SCHEMA: typeTwo = single sensor reference, typeThree =
fixed value or sensor, typeFour = list of sensors), resolving the todo
about the field type living hardcoded in asset_context.html in 3 places.
The template now derives its sensor-only check from the schema, so new
context fields (e.g. the upcoming commodities and commitments editors)
only need a schema entry. No behaviour change.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016MLCUiSdXDqDBmg8GbYp1B

* feat(ui): edit per-commodity flex-contexts through a commodity tab bar (#2230)

The flex-context modal gains a pill bar: 'electricity' (the top-level
context) plus one pill per entry of the commodities list, with add/remove
affordances. The existing card editor is reused per scope; the add-field
dropdown only offers fields that CommodityFlexContextSchema shares (driven
by a new per-commodity flag on UI_FLEX_CONTEXT_SCHEMA entries). Saving
PATCHes the whole flex-context including the nested commodities list.

Also documents the commodities field (new COMMODITIES metadata + docs row)
and removes it from the UI-schema exclusion list.

Verified end-to-end against a live server with a seeded multi-commodity
asset: per-scope editing, adding/removing commodities, duplicate-name
rejection, and round-tripping through PATCH + reload.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016MLCUiSdXDqDBmg8GbYp1B

* refactor: derive UI flex-context field types from DBFlexContextSchema

Per review on #2281: define each type token's UI description once
(UI_TYPE_DESCRIPTIONS) instead of repeating it per field, and derive the
backend type of each UI_FLEX_CONTEXT_SCHEMA... (continued)

3 of 3 new or added lines in 1 file covered. (100.0%)

15850 of 19129 relevant lines covered (82.86%)

0.83 hits per line