FlexMeasures / flexmeasures / 27687603307

81%

push

github

Feat: filter sensors and assets by ID (#2231)

* feat/api: add ID to the filterable fields in sensors and assets API endpoints

Signed-off-by: Nicolas Höning <nicolas@seita.nl>

* allow to search by ID prefix as well, more aligning with how search works for the other fields

Signed-off-by: Nicolas Höning <nicolas@seita.nl>

* complete changelog entry

Signed-off-by: Nicolas Höning <nicolas@seita.nl>

* fix(api): require asset read access for sensors

Protect GET /assets/<id>/sensors with the same read permission guard as the asset detail endpoint, with a regression test for cross-organisation access.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* fix(api): honor all asset sensor filter terms

Use the SearchFilterField output directly so multi-term and quoted searches behave like the other filtered endpoints.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* fix(api): keep ID prefix filters indexable

Replace text casts on integer IDs with equality and range predicates, and tighten fresh-db coverage with prefix decoys and exact counts.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* docs(api): document ID prefix search behavior

Expose the filter metadata in the asset and sensor schemas and clarify that ID prefixes return only matching records.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* fix(api): remove duplicate asset filter fields

Rely on PaginationSchema for inherited filter parameters and refresh the generated OpenAPI spec.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* fix(api): explain no-match ID prefix filter

Document that false() makes the ID-prefix branch match no rows for non-canonical digit strings.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* refactor(api): clarify ID prefix digit naming

Rename the ID-prefix helper argument so it is clear the original digit string is needed for ran... (continued)

36 of 38 new or added lines in 4 files covered. (94.74%)

13407 of 16562 relevant lines covered (80.95%)

0.81 hits per line