In the previous part I introduced the Result class as a means of control flow and error handling. Now I will focus on when to use the Result class to return an Error, and when to throw instead.
Part of Functional Programming: Clean architecture and DDD series
There appears to…
When we add more functional composition tools to our belt, we can start composing usecase pipelines that are both terse and descriptive.
Part of Functional Programming: Clean architecture and DDD series
map: (value => newValue) => Result<newValue, ...>flatMap: (value => newResult) => newResulttoTup: (value =>…We can improve our error handling and composition by leveraging a Result class and several other tools from the functional programming world.
Part of Functional Programming: Clean architecture and DDD series
Instead of throwing errors, we wrap our results. Either the Result is an Error value, or a Success value…
Recently, often the question is asked if Hooks and Context replaces Redux. It is more a question of do you need Redux, and perhaps how Hooks and Context can help you write cleaner, more functional, more composable code.
Part of Of Hooks and Screens series
Hooks by themselves are an…
