Update upstream error classification to match current API client errors

The API client consolidates response decoding into a single code path
that produces "decoding response" errors instead of the previous
"decoding savings" / "decoding stores" / "reading response" variants.
Update classifyCLIError to match the current error strings, and add
"fetching savings" alongside the existing "fetching deals" / "fetching
stores" cases.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-02-23 01:31:55 -05:00
parent 28479071ae
commit f486150c06

View File

@@ -175,10 +175,9 @@ func classifyCLIError(err error) *cliError {
} }
case strings.Contains(lowerMsg, "unexpected status"), case strings.Contains(lowerMsg, "unexpected status"),
strings.Contains(lowerMsg, "executing request"), strings.Contains(lowerMsg, "executing request"),
strings.Contains(lowerMsg, "reading response"), strings.Contains(lowerMsg, "decoding response"),
strings.Contains(lowerMsg, "decoding savings"),
strings.Contains(lowerMsg, "decoding stores"),
strings.Contains(lowerMsg, "fetching deals"), strings.Contains(lowerMsg, "fetching deals"),
strings.Contains(lowerMsg, "fetching savings"),
strings.Contains(lowerMsg, "fetching stores"), strings.Contains(lowerMsg, "fetching stores"),
strings.Contains(lowerMsg, "finding stores"): strings.Contains(lowerMsg, "finding stores"):
return &cliError{ return &cliError{