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
Operations such as lists.batch_subscribe return errors in an errors array, rather than a single error value that the response handler expects. At the moment if an error occurs during that operation gibbon silently returns.
As we can't raise individual errors for each error in the array we have two choices:
Raise a Gibbon::MailChimpError for the first error in the array
Introduce a new Gibbon::MultipleMailChimpErrors to encapsulate all of the errors
Thoughts?
The text was updated successfully, but these errors were encountered:
The trouble with raising an error in batch cases is the caller wouldn't have the information to handle the successful portion of the response. This makes building apps that sync lists with MailChimp tough. And I don't believe the successful portion of the response belongs in the error.
Would raising an error if all of the batched items fail be helpful?
Operations such as
lists.batch_subscribe
return errors in anerrors
array, rather than a singleerror
value that the response handler expects. At the moment if an error occurs during that operation gibbon silently returns.As we can't raise individual errors for each error in the array we have two choices:
Gibbon::MailChimpError
for the first error in the arrayGibbon::MultipleMailChimpErrors
to encapsulate all of the errorsThoughts?
The text was updated successfully, but these errors were encountered: