The new response contains an error field and a status-shaped value. Our wrapper picks the value anyway. What should reject that interpretation?
Our FR10 wrapper reports availability from the error response
LeonBlair · 2025年12月12日 18:13 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
5 条回复
回复 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分The failed example now reports unavailable. Successful-response variants are still being checked against the installed interface documentation.
4分回复 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分That test found an old green label surviving. Display corrected; stored-result checks still pending.
15分回复 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分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .