What changed
Producer-side tools call this additive. It breaks exhaustive switches, strict parsers and generated client enums.
Affects this value on PlaidErrorType reachable from 280 operations.
New value: BASE_REPORT_ERROR.
can now return "BASE_REPORT_ERROR"
Who is affected
Code that reads Plaid's PlaidErrorType objects, used by 280 Plaid operations.
Before and after
| Where | Before | After |
|---|---|---|
| PlaidErrorType | "API_ERROR", "ASSET_REPORT_ERROR", "BANK_TRANSFER_ERROR", "CHECK_REPORT_ERROR", "CONSUMER_REPORT_ERROR", "INCOME_VERIFICATION_ERROR", "INSTITUTION_ERROR", "INVALID_INPUT", "INVALID_REQUEST", "INVALID_RESULT", "ITEM_ERROR", "MICRODEPOSITS_ERROR", "OAUTH_ERROR", "PARTNER_ERROR", "PAYMENT_ERROR", "RATE_LIMIT_EXCEEDED", "RECAPTCHA_ERROR", "SANDBOX_ERROR", "SIGNAL_ERROR", "TRANSACTIONS_ERROR", "TRANSACTION_ERROR", "TRANSFER_ERROR", "USER_ERROR" | "API_ERROR", "ASSET_REPORT_ERROR", "BANK_TRANSFER_ERROR", "BASE_REPORT_ERROR", "CHECK_REPORT_ERROR", "CONSUMER_REPORT_ERROR", "INCOME_VERIFICATION_ERROR", "INSTITUTION_ERROR", "INVALID_INPUT", "INVALID_REQUEST", "INVALID_RESULT", "ITEM_ERROR", "MICRODEPOSITS_ERROR", "OAUTH_ERROR", "PARTNER_ERROR", "PAYMENT_ERROR", "RATE_LIMIT_EXCEEDED", "RECAPTCHA_ERROR", "SANDBOX_ERROR", "SIGNAL_ERROR", "TRANSACTIONS_ERROR", "TRANSACTION_ERROR", "TRANSFER_ERROR", "USER_ERROR" |
Code that breaks
switch (response) {
// existing branches …
// no branch for "BASE_REPORT_ERROR"
default:
throw new Error("unexpected value");
}Based on Plaid’s published API specification. How severity is decided.