FlexMeasures / flexmeasures / 29588842972

82%

push

github

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

* 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

* 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 entry from the corresponding
DBFlexContextSchema field. Commitments are now correctly typed as a list
of structured entries (new typeSix token) rather than fixed-or-sensor.
Sensor-only exceptions that live in validators rather than field types
(fixed prices forbidden in the DB, aggregate-power requiring a sensor)
are listed explicitly with pointers to those validators.

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

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

15 of 19 new or added lines in 1 file covered. (78.95%)

14805 of 18137 relevant lines covered (81.63%)

0.82 hits per line