You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Six items in the tool-surface-redesign epic (#31) are blocked on capabilities the StatusPro server doesn't yet expose. The probes in #30 confirmed each unsupported parameter is silently ignored — there's no client-side workaround that doesn't 10x the round-trip count.
Today the issues exist locally but nothing tracks whether we've actually filed them upstream with the StatusPro team. This issue closes that loop.
Items to file with StatusPro
Each links to the local issue (which has the full motivation + probe results) — the upstream filing should reference these so context isn't duplicated.
Why
Six items in the tool-surface-redesign epic (#31) are blocked on capabilities the StatusPro server doesn't yet expose. The probes in #30 confirmed each unsupported parameter is silently ignored — there's no client-side workaround that doesn't 10x the round-trip count.
Today the issues exist locally but nothing tracks whether we've actually filed them upstream with the StatusPro team. This issue closes that loop.
Items to file with StatusPro
Each links to the local issue (which has the full motivation + probe results) — the upstream filing should reference these so context isn't duplicated.
GET /orders?id[]=…batch fetchGET /orders?updated_since=ISO8601filter (requires server to exposeupdated_aton orders)POST /orders/bulk-statusreturns per-order outcomes (job_id + poll, or inline array)GET /orders?overdue=true+?sort=filtersGET /orders?customer_email=exact-match filterGET /orders/summary(or equivalent) aggregation endpointAcceptance
Notes