AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
Is There a Reason for Throwing Stacks in C L I?
Air constructors now have an optional cause field in their options object. So you can like, catch a throw and then add more contect by creating a new air with a cause of the caught air. Another thing we could talk about two similar to the reason field. People don't care what language your s l i tool is written in. If you're throwing stacks in, they're there in front of user. They're not really actionable by the userr other than, maybe a nice one will copy and paste that into a get hub issue. You don't need to just throw and ndump a stack trace, because nobody should have to care about that. In a perfect world