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

I generally recommend a set of custom errors that extend the base error class.

You can also have a http code as part of each custom error

Wrap your API with a global error handler that gets uncaught errors and completes with error response 

Then, when throws occur your api now automagically have relevant status codes and good messages

pretty sure this is what i was looking at doing before xmas but got distracted by feature building again. now suffering debugging pain from not implementing proper error classes

Designing and building AI systems

https://agents.gladio.ai

ChatGPT is definitely your fren to get this one kickstarted, very little relation with app logic, super LLM friendly task