FlexMeasures / flexmeasures / 40853042095

87%

main: 87%

Pull #2767

github

Look up the fields a sensor's deletion affects only once the user clicks to delete it

Finding them means searching every asset's flex-config, which the sensor page did on each view by a user who may delete the sensor, although the result is only needed on deletion.
The delete button now fetches the confirmation note and the toast from a UI endpoint, GET /sensors/<id>/deletion-notes, which requires delete access.
It is a UI endpoint rather than part of API v3, so its response may change, e.g. once a sensor's references are reported more widely.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DWv6v4GGZAdqXymjP6pMLk
Signed-off-by: F.N. Claessen <claessen@seita.nl>

91 of 94 new or added lines in 5 files covered. (96.81%)

22499 of 25858 relevant lines covered (87.01%)

0.87 hits per line