1840929 - Decide how to handle invalid API responses

Status: RESOLVED INCOMPLETE

(Firefox Graveyard :: Shopping, task, P3)

Description

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

During the initial dev period, we are validating the server responses against a schema, but we're just dumping schema validation errors to the console, because both the API and the schemas are changing quickly.

When we get closer to release, we'll want to reassess whether it makes sense to handle invalid responses. Do we log a telemetry event?

We'll want to figure out the potential cases and actions we'd like to take, and tailor the code decision to help us keep server and client in sync.

Comment 1

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Marking 119 ship-blockers as P1s for easier tracking

Comment 2

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Kicking out of the 119 blockers list.

Comment 3

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Moving "fast follow" items to top-level in the shopping backlog. Apologies for bug spam

Comment 4

[David Lawrence [:dkl]]

This bug is being closed because we are closing the Bugzilla component.
If this still needs attention, please re-open and change component to
the appropriate component or "General".