Edge Case Poisoning
buttondown.email
buttondown.email
I wonder if there would be a way to have “sum models” so you can have the happy path recipe plus one of the exceptions so a single API lets you only see the exceptions you care about, not all of them… although that way the API consumer needs to be prepared to receive a new, unknown exception, so you need to have either a higher level of abstraction (as mentioned in the link) or an interactive session with the API where you can do something akin to common lisp conditions: receive an unwound exception and return a way forward for the new exception. (sorry for the ramble; on phone)