Unwrapit provides a way to handle errors in JS/TS
musicq.gitbook.io
Unwrapit provides a way to handle errors in JS/TS
1–10 of 72 posts
Re: Unwrapit provides a way to handle errors in JS/TS
#2Spent sometime to complete the document of my rust Result like library `unwrapit` for JS/TS.
Still think this might be a proper way to deal with errors in JS/TS
Re: Unwrapit provides a way to handle errors in JS/TS
#3Spent sometime to complete the document of my rust Result like library `unwrapit` for JS/TS. Still think this might be a proper way to deal with errors in JS/TS
This is interesting. Does it have any performance impact?
Re: Unwrapit provides a way to handle errors in JS/TS
#4Would be nice if this didn't have a dependency on rxjs just for a single use of Observable
Re: Unwrapit provides a way to handle errors in JS/TS
#5For anyone who has NOT written in rust yet, there's nothing in the readme that explains what's intuitive or easy about the library. It doesn't even explain what to expect as the `status` getting logged, not go mention other possible values.
Re: Unwrapit provides a way to handle errors in JS/TS
#6Spent sometime to complete the document of my rust Result like library `unwrapit` for JS/TS. Still think this might be a proper way to deal with errors in JS/TS
This is awesome! I dig this when using Rust and am pumped to try and sneak this in at work where we have a large TS codebase.
Re: Unwrapit provides a way to handle errors in JS/TS
#7This is sort of saying "exceptions were a mistake", right?
Re: Unwrapit provides a way to handle errors in JS/TS
#8Why not expect that something would throw at some point where app logics are taking place and wrap with try-catch at your lower layer and handle uncaught errors there?
Adding all these boilerplate that not all people agree with would just make it harder to read and debug.
Re: Unwrapit provides a way to handle errors in JS/TS
#9Just use a library that already contains this and more functional programming idioms, like fp-ts or its successor, Effect [0]. It is a little more complex to learn but much more robust that simply implementing your own Result and other types.
Re: Unwrapit provides a way to handle errors in JS/TS
#10Spent sometime to complete the document of my rust Result like library `unwrapit` for JS/TS. Still think this might be a proper way to deal with errors in JS/TS
I think the idea of try/catch is to let the error bubble up to the place where it can be handled. It usually results into having error handling in a few central places. Your example in github is IMO not how to make best use of try/catch.
Here’s lots of typical exception handling patterns: http://wiki.c2.com/?ExceptionPatterns
Persobally I prefer exceptions over boilerplate “if’s”, but good to know that there’s a wrapper for the people who don’t.