As one initially starts practising functional programming with tiny single purpose pure functions, one gets to a point where the composition of those functions seems awkward.
Let's say we are extracting the results from a League of Legends match from the Riot API. In a functional programming style, we could break this down into a series of functions.
The actual code that composes these functions together would look like.
But isn't it strange that the data flows right to left, which is backwards when reading the code from left to right? This is what I mean by inside-out functional programming. This consumes mental energy by having the reader start from the end.
We can attempt to solve this problem by introducing intermediate variables.
But then this introduces a new problem.
result2 are clearly poorly named and we could make up better ones. However, this is just noise. We don't care about the names for
result2, we only wanted the data flow to match the code flow.
What we really want is something that looks like,
One might recognize this if rewritten in a different way.
It's the pipe operator!
There are a few ways to use the pipe operator in our code today.
Notice how ramda takes the approach of composing functions using pipe, whereas ts-belt takes a data-first approach where match is the first argument into pipe.
The work-in-progress syntax is definitely controversial, but it does solve our original problem having the data flow match the code flow.
Do you want to get more things done by saving your mental energy for more important things, like esports? You’re in luck, Battlefy is hiring.