What's your go-to for error handling? Exceptions or returning an object? - ThreadSky

itsbukola.bsky.social • 58 days ago

What's your go-to for error handling? Exceptions or returning an object?

1 / 2

Comments

georg.dev•57 days ago

Good question! For me, it depends on the scope and complexity of the project:

- If it's only a few DB calls and low complexity, I'd go with just throwing the error.
- If it's a large and complex project, I'd use TypeScript with Effect (see screenshot).

itsbukola.bsky.social•57 days ago

Oh this is cool. I didn't know of Effect before now

georg.dev•57 days ago

I can really recommend it for large projects. It's a great library. You sacrifice adding some boilerplate but you get type-safe error handling and stronger guarantees.

itsbukola.bsky.social•57 days ago

I will check it out

amentler.bsky.social•57 days ago

Is it possible under normal circumstances that a not authorized person gets to that call?
If not: its a hacker. throw exception. Catch it later or break the app. Doesnt matter.

If its possible try:
If lsAllowedToDoStuff()
DoStuff() //see above. Throws exception.

amentler.bsky.social•57 days ago

Its an old religious discussion.
I would read about how other languages handle that (java, c#, rust)

The exception mechanism in typescript isn't an accident but a decision that may not be loved universally.

Btw think about this:
https://stackoverflow.com/questions/63526969/how-do-you-return-multiple-values-from-a-typescript-function
Result/exception without nesting

itsbukola.bsky.social•57 days ago

So exception regardless? Nice

Actually, it's not possible under normal circumstances for an unauthorized person to get the call

amentler.bsky.social•57 days ago

Its my preference for this kind of problem but in the end i think in most cases it really doesnt matter which way a team decides to go as long as they have a usable common standard that fits their work environment.

timberjustinlake.bsky.social•57 days ago

Always prefer returning if possible, TypeScript can't narrow or even tell you if a function throws so without meticulous documentation and diligent reading of said documentation you don't know what, if any, errors will be thrown. Returned errors force you to deal with them.

itsbukola.bsky.social•57 days ago

Yes, I like to see the specific source of problems rather than a random vague error

Comments

Posting Rules

Reply