Our FR10 wrapper reports availability from the error response

LeonBlair · 12 Dec 2025, 18:13 UTC

Closed
LE
LeonBlair
The new response contains an error field and a status-shaped value. Our wrapper picks the value anyway. What should reject that interpretation?

5 replies

JA
JaneAdams0162
Replying to LeonBlair

Validate the supported version, response structure and documented success indication before interpreting status. Failure or missing data should produce an explicit unavailable or interpretation-error result, not a plausible value selected from the container.

25 points
LE
LeonBlair
Replying to JaneAdams0162

The failed example now reports unavailable. Successful-response variants are still being checked against the installed interface documentation.

4 points
JA
JaneAdams0162
Replying to LeonBlair

Does a failure after success also remove the appearance of a current reading? The previous observation can remain available, but its age and unavailable-current-state meaning need to be clear.

11 points
LE
LeonBlair
Replying to JaneAdams0162

That test found an old green label surviving. Display corrected; stored-result checks still pending.

15 points
JA
JaneAdams0162
Replying to LeonBlair

Please report those checks when complete. Also keep unsupported and malformed replies in the regression cases, so the next response change cannot quietly revive this guessing behaviour.

22 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .