简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

dashboard finds a cheerful status inside a failed reply

MiaAli0209 · 2025年9月27日 13:20 UTC

已关闭
MI
MiaAli0209
Our separate FR5 diagnostic screen has joined the optimistic-display club. The rebuilt environment returns a structured reply where the old helper expected one value, and a failed request can now produce a perfectly plausible status. I've stopped using the tile for maintenance decisions. Is this a case for separate version adapters, or am I making a simple parser fix unnecessarily grand?

3 条回复

HE
HenryBrown0873
回复 MiaAli0209

First establish the documented return contract for each supported SDK version. Then map successful replies into one internal result shape and reject unsuccessful or malformed replies explicitly. Whether that takes one adapter or two is a smaller question than preventing another plausible fallback.

6
MI
MiaAli0209

Developer found our fallback: any nonempty reply was accepted and its first value sent to the display. We have version-linked examples now. Failed requests show unavailable in the offline checks, with the previous good reading kept separately and marked old.

9
HE
HenryBrown0873
回复 MiaAli0209

Include an unsupported version and a success-looking reply with a missing field. A parser that rejects recognised failures can still be too trusting about everything it does not recognise.

12

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .