@saber2pr/fp

@saber2pr/fp

functional programing in async | sync | lazy.

# from npm
npm install @saber2pr/fp

# from github
git clone https://github.com/Saber2pr/fp.git

Why

If you often program with node.js, there will be some bad cases in async, like this:

const contents = await Promise.all(
  ['./1.txt', './2.txt'].map(async file_name => ({
    content1: await readFile(file_name).then(buffer => buffer.toString()),
    content2: await readFile(file_name).then(buffer => buffer.toString())
  }))
)

then you get a bad result, the contents.content1 and contents.content2 is a Promise

How to deal with it?

Now, there is a function named async_map to it:

const contents = async_map(['./1.txt', './2.txt'], async file_name => ({
  content1: await readFile(file_name).then(buffer => buffer.toString()),
  content2: await readFile(file_name).then(buffer => buffer.toString())
}))

you will get a result and the contents.content1 and contents.content2 is the correct type "string".

what's more...

API

compose

pipe

setter

async_reduce

async_reduceRight

async_compose

async_pipe

async_setter

async_forEach

async_filter

async_intercept

async_map

*range

*map

*filter

*reduce

toIt

from

---

start

npm install

npm start

npm test

Author: saber2pr

---

develope and test

you should write ts in /src

you should make test in /src/test

export your core in /src/index.ts!