SamCarter1029 · 17 Nov 2025, 20:33 UTC
Check the documented return shape for the exact SDK version before indexing it. Save one successful and one failed response with their versions so the wrapper change has something concrete to be tested against.
7 pointsEstablish whether that interpreted status is used only for display or also by another part of the application, because the same parsing error may have more than one visible effect.
13 pointsDisplay only, Kai. The wrapper takes the first value without checking request success.
20 pointsSam, do you still need to support both SDK versions? That changes whether one replacement parser is enough or the maintainer needs two explicit input formats behind the same display.
-3 pointsLuca, I would want the supported-version list in the handover either way. We have bought software updates before discovering nobody agreed how long the older setup would remain supported.
20 pointsBoth versions for now, Luca. Different teaching laptops. Maintainer has examples from each.
13 pointsUse version-specific interpretation behind one clear display result. Unsupported shapes should fail visibly, not be guessed into whichever old format is easiest to accept.
16 pointsJasper, thanks, that is the ownership question I was circling. Sam, who updates the examples and parser when another SDK version is introduced?
21 pointsCourse software maintainer. Added supported versions and the update check to the handover draft.
14 pointsInclude a failed request following a successful reading, so the screen does not leave the old value looking current when the new parser correctly reports failure.
16 pointsAnd failure before the first successful read. No historical value exists in that case, even if the widget arrives with a cheerful default.
25 pointsBoth cases added. Failed current read shows unavailable; previous reading stays separately marked last known.
18 pointsDoes the previous reading retain its time and source laptop or connection identity? That would help someone using two setups avoid treating the last good display as belonging to the current session.
4 pointsAlso have a student read those states, Sam. Ask what is known now, not whether the revised screen looks nice.
9 pointsTime and connection identity retained, Jasper. Student walkthrough scheduled; malformed replies still need coverage.
15 pointsInclude missing required data and wrong field types in those malformed cases. A response can say success and still lack the information the display requires.
7 pointsDid the walkthrough distinguish unavailable now from that last-known reading? Interested whether the words carry the difference without an explanation from the maintainer.
19 pointsThis discussion is closed to new replies after six months without activity. Last activity: .