A place for developers to talk about building on Farcaster.

/dev

rapidly learning that i need a standardized error method with bubbling. are the errors from the database, from the biz logic or from the api query? would like error context to bubble appropriately. 

am very sure i am currently doing it on hard mode with throws that don't communicate context well

Gamer, educator, dev translator | building tabletop.xyz | Writings, memes, thoughts, and mints in /nerdery | lead /tabletop /gaming /sobriety

In my experience, the most important thing about handling exceptions is mapping them to recoverable vs unrecoverable to facilitate retry logic. Very rarely do you care whether the exception came from the database. What matters is, can the error be retried (locally or by the client)? Or should the call fail immediately?