• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

FlexMeasures / flexmeasures / 37283095033
88%

Build:
DEFAULT BRANCH: main
Ran 05 Oct 2026 08:32AM UTC
Jobs 1
Files 188
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

05 Oct 2026 08:21AM UTC coverage: 86.329% (+0.01%) from 86.319%
37283095033

push

github

web-flow
Refuse a key no sensor reference has, and say where each spelling belongs (#2656)

* data/schemas/sensors: refuse a key a sensor reference does not take

This field reads the keys it knows and read past the rest, so a key it does not know was accepted and did nothing: a filter written as source-type rather than source-types dropped the filtering it was meant to apply, silently. A forecaster's references never had this problem, as they load through the marshmallow schema, which refuses unknown fields.

The keys a reference takes are read off that schema rather than written out again, so a key added there is accepted here without a second list to remember.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* docs/changelog: link the refusal of unknown reference keys to its pull request

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* docs/api: say in the API change log that a reference refuses a key it does not take

An API-visible refusal where a payload used to be accepted belongs there as well as in the main changelog.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* docs: say what a reference takes, not only what it refuses

The sentence sat right after the source-filter keys, so it read as though those were all a reference takes, which the default and the cleaning bounds below it contradict.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* data/schemas/sensors: read a source filter written in the singular, and refuse a key no reference has

A key that takes a list may name a single value when written in the singular, which is the notation the API documentation has always used, and which the data endpoints' own filters are named in: 'source' says what 'sources' says, and 'source-type' what 'source-types' says. A sensor refere... (continued)

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

20946 of 24263 relevant lines covered (86.33%)

0.86 hits per line

Jobs
ID Job ID Ran Files Coverage
1 37283095033.1 05 Oct 2026 08:32AM UTC 188
86.33
GitHub Action Run
Source Files on build 37283095033
  • Tree
  • List 188
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #37283095033
  • bf05a1bb on github
  • Prev Build on main (#37244393992)
  • Next Build on main (#37316548867)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc