关于 fp-ts Pipe and Flow Composition
面向使用 TypeScript 和 fp-ts 的开发者,介绍用 pipe 与 flow 组合函数的实践指南。涵盖即时执行与可复用管道,以及与 fp-ts 数据类型结合的模式。
主要功能
- 01区分 pipe 与 flow 的执行方式
- 02组合数组、字符串等转换
- 03串联 Option、Either 与异步类型
- 04提供类型推断与调试建议
适用场景
- 01立即转换已有值
- 02定义可复用的数据处理流程
- 03组合可能失败或异步的操作
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ whatiskadudoing/ fp-ts-skills --skill fp-ts-pipe-and-flow-composition安装后在 Claude Code 中输入/fp-ts-pipe-and-flow-composition确认已加载。
详细介绍
fp-ts Pipe 和 Flow 组合
函数组合是函数式编程的核心。fp-ts 提供了两个强大的函数组合工具:pipe 和 flow。本指南涵盖了构建优雅、类型安全的流水线所需的一切。
导入
import { pipe, flow, identity } from 'fp-ts/function'
理解 Pipe 和 Flow 的区别
pipe:从起始值开始立即执行
pipe 接收一个值,并将其传递给一系列函数,立即执行这些函数。
// pipe(value, fn1, fn2, fn3) === fn3(fn2(fn1(value)))
const result = pipe(
5,
n => n * 2, // 10
n => n + 1, // 11
n => `Result: ${n}` // "Result: 11"
)
在以下情况使用 pipe:
- 你已有一个值,并希望立即对其进行转换
- 构建一次性转换
- 使用 fp-ts 数据类型(Option、Either、Task 等)
- 需要清晰、从上到下的数据流
flow:创建可复用的流水线
flow 将函数组合成一个新函数,但不执行它们。
// flow(fn1, fn2, fn3) === (x) => fn3(fn2(fn1(x)))
const processNumber = flow(
(n: number) => n * 2,
n => n + 1,
n => `Result: ${n}`
)
processNumber(5) // "Result: 11"
processNumber(10) // "Result: 21"
在以下情况使用 flow:
- 创建可复用的转换
- 定义要作为回调传递的函数
- 构建可组合的工具函数
- 你还没有输入值
快速对比
| 方面 | pipe | flow |
|---|---|---|
| 执行方式 | 立即 | 延迟 |
| 第一个参数 | 值 | 函数 |
| 返回值 | 转换后的值 | 新函数 |
| 使用场景 | 立即转换数据 | 创建可复用的转换 |
// These are equivalent:
const result1 = pipe(5, double, increment, toString)
const result2 = flow(double, increment, toString)(5)
处理不同元数的函数
一元函数(单个参数)
大多数 fp-ts 操作都会返回一元函数,因此非常适合组合。
import { pipe } from 'fp-ts/function'
import * as A from 'fp-ts/Array'
const numbers = [1, 2, 3, 4, 5]
const result = pipe(
numbers,
A.filter(n => n % 2 === 0),
A.map(n => n * 10)
)
// [20, 40]
处理多参数函数
需要使用多参数函数时,请使用柯里化或部分应用。
// Method 1: Inline arrow function
const add = (a: number, b: number) => a + b
pipe(
5,
n => add(n, 10), // Wrap in arrow function
n => n * 2
)
// Method 2: Curried version
const addCurried = (b: number) => (a: number) => a + b
pipe(
5,
addCurried(10), // Clean composition
n => n * 2
)
// Method 3: Using fp-ts curry utilities
import { curry2 } from 'fp-ts-std/Function'
const addC = curry2(add)
pipe(
5,
addC(10),
n => n * 2
)
数据转换流水线
数组转换
import { pipe } from 'fp-ts/function'
import * as A from 'fp-ts/Array'
import * as NEA from 'fp-ts/NonEmptyArray'
interface User {
id: number
name: string
age: number
active: boolean
}
const users: User[] = [
{ id: 1, name: 'Alice', age: 30, active: true },
{ id: 2, name: 'Bob', age: 25, active: false },
{ id: 3, name: 'Charlie', age: 35, active: true },
]
// Complex transformation pipeline
const activeUserNames = pipe(
users,
A.filter(u => u.active),
A.map(u => u.name),
A.sort(S.Ord)
)
// ['Alice', 'Charlie']
// With grouping
import * as R from 'fp-ts/Record'
import * as S from 'fp-ts/string'
const usersByActiveStatus = pipe(
users,
A.groupBy(u => u.active ? 'active' : 'inactive')
)
// { active: [...], inactive: [...] }
Record/Object 转换
import { pipe } from 'fp-ts/function'
import * as R from 'fp-ts/Record'
const scores: Record<string, number> = {
alice: 85,
bob: 92,
charlie: 78
}
const adjustedScores = pipe(
scores,
R.map(score => score * 1.1),
R.filter(score => score >= 85)
)
字符串转换
import { pipe, flow } from 'fp-ts/function'
import * as S from 'fp-ts/string'
const normalizeString = flow(
S.trim,
S.toLowerCase,
s => s.replace(/\s+/g, '-')
)
const slug = normalizeString(' Hello World ') // 'hello-world'
// With validation
import * as O from 'fp-ts/Option'
const safeSlug = flow(
O.fromPredicate((s: string) => s.length > 0),
O.map(normalizeString)
)
与 fp-ts 数据类型组合
使用 Option
import { pipe } from 'fp-ts/function'
import * as O from 'fp-ts/Option'
interface Config {
database?: {
host?: string
port?: number
}
}
const getConnectionString = (config: Config): O.Option<string> =>
pipe(
O.fromNullable(config.database),
O.flatMap(db => O.fromNullable(db.host)),
O.map(host => `postgresql://${host}`)
)
// Chaining multiple Option operations
const findUser = (id: number): O.Option<User> => { /* ... */ }
const getUserEmail = (user: User): O.Option<string> => { /* ... */ }
const validateEmail = (email: string): O.Option<string> => { /* ... */ }
const getValidatedEmail = (userId: number): O.Option<string> =>
pipe(
findUser(userId),
O.flatMap(getUserEmail),
O.flatMap(validateEmail)
)
使用 Either
import { pipe } from 'fp-ts/function'
import * as E from 'fp-ts/Either'
type ValidationError = { type: 'validation'; message: string }
type NetworkError = { type: 'network'; message: string }
type AppError = ValidationError | NetworkError
const validateAge = (age: number): E.Either<ValidationError, number> =>
age >= 0 && age <= 150
? E.right(age)
: E.left({ type: 'validation', message: 'Invalid age' })
const validateName = (name: string): E.Either<ValidationError, string> =>
name.length >= 2
? E.right(name)
: E.left({ type: 'validation', message: 'Name too short' })
// Sequential validation (fail on first error)
const validateUser = (name: string, age: number) =>
pipe(
E.Do,
E.bind('name', () => validateName(name)),
E.bind('age', () => validateAge(age)),
E.map(({ name, age }) => ({ name, age, createdAt: new Date() }))
)
// Accumulating errors with Validation
import * as A from 'fp-ts/Apply'
import * as NEA from 'fp-ts/NonEmptyArray'
type ValidationErrors = NEA.NonEmptyArray<string>
type Validation<A> = E.Either<ValidationErrors, A>
const applicativeValidation = E.getApplicativeValidation(NEA.getSemigroup<string>())
const validateUserAll = (name: string, age: number) =>
pipe(
A.sequenceS(applicativeValidation)({
name: validateName(name),
age: validateAge(age)
}),
E.map(({ name, age }) => ({ name, age }))
)
使用 Task 和 TaskEither
import { pipe } from 'fp-ts/function'
import * as T from 'fp-ts/Task'
import * as TE from 'fp-ts/TaskEither'
// Composing async operations
const fetchUser = (id: number): TE.TaskEither<Error, User> =>
TE.tryCatch(
() => fetch(`/api/users/${id}`).then(r => r.json()),
(error) => new Error(String(error))
)
const fetchUserPosts = (userId: number): TE.TaskEither<Error, Post[]> =>
TE.tryCatch(
() => fetch(`/api/users/${userId}/posts`).then(r => r.json()),
(error) => new Error(String(error))
)
const getUserWithPosts = (id: number): TE.TaskEither<Error, UserWithPosts> =>
pipe(
fetchUser(id),
TE.flatMap(user =>
pipe(
fetchUserPosts(user.id),
TE.map(posts => ({ ...user, posts }))
)
)
)
// Parallel execution
import * as A from 'fp-ts/Array'
const fetchAllUsers = (ids: number[]): TE.TaskEither<Error, User[]> =>
pipe(
ids,
A.map(fetchUser),
A.sequence(TE.ApplicativePar) // Parallel execution
)
使用 Reader 和 ReaderTaskEither
import { pipe } from 'fp-ts/function'
import * as RTE from 'fp-ts/ReaderTaskEither'
interface Dependencies {
userRepo: UserRepository
emailService: EmailService
logger: Logger
}
const getUser = (id: number): RTE.ReaderTaskEither<Dependencies, Error, User> =>
pipe(
RTE.ask<Dependencies>(),
RTE.flatMapTaskEither(deps => deps.userRepo.findById(id))
)
const sendWelcomeEmail = (user: User): RTE.ReaderTaskEither<Dependencies, Error, void> =>
pipe(
RTE.ask<Dependencies>(),
RTE.flatMapTaskEither(deps => deps.emailService.send(user.email, 'Welcome!'))
)
const onboardUser = (id: number): RTE.ReaderTaskEither<Dependencies, Error, User> =>
pipe(
getUser(id),
RTE.tap(sendWelcomeEmail),
RTE.tap(user =>
RTE.fromTask(deps => deps.logger.info(`Onboarded: ${user.name}`))
)
)
编写清晰流水线的最佳实践
1. 保持函数小巧且专注
// Good: Each step does one thing
const processOrder = pipe(
order,
validateOrder,
calculateTotals,
applyDiscounts,
formatForDisplay
)
// Avoid: Large inline functions
const processOrder = pipe(
order,
o => {
// 50 lines of validation, calculation, and formatting
}
)
2. 提取具名函数以提高清晰度
// Good: Named functions explain intent
const isAdult = (user: User) => user.age >= 18
const formatName = (user: User) => `${user.firstName} ${user.lastName}`
const adultNames = pipe(
users,
A.filter(isAdult),
A.map(formatName)
)
// Less clear: Anonymous functions inline
const adultNames = pipe(
users,
A.filter(u => u.age >= 18),
A.map(u => `${u.firstName} ${u.lastName}`)
)
3. 使用 flow 创建可复用的转换
// Define reusable pipelines
const normalizeEmail = flow(
S.trim,
S.toLowerCase
)
const validateEmailFormat = flow(
O.fromPredicate((s: string) => s.includes('@')),
O.filter(s => s.length >= 5)
)
// Compose them
const processEmail = flow(
normalizeEmail,
validateEmailFormat
)
4. 将相关操作分组
// Good: Logical grouping with comments
const processUsers = pipe(
users,
// Filter
A.filter(isActive),
A.filter(isVerified),
// Transform
A.map(enrichWithMetadata),
A.map(formatForAPI),
// Sort
A.sort(byCreatedAt)
)
5. 在合适的层级处理错误
// Good: Handle errors where you can meaningfully respond
const getUserSafely = (id: number) =>
pipe(
fetchUser(id),
TE.mapLeft(toAppError),
TE.orElse(error =>
error.type === 'not_found'
? TE.right(defaultUser)
: TE.left(error)
)
)
6. 使用 Do 记法处理复杂依赖
// Good: Clear when steps depend on previous results
const createOrder = pipe(
E.Do,
E.bind('user', () => validateUser(userData)),
E.bind('items', () => validateItems(itemsData)),
E.bind('shipping', ({ user }) => calculateShipping(user.address)),
E.bind('total', ({ items, shipping }) => calculateTotal(items, shipping)),
E.map(({ user, items, total }) => ({ user, items, total }))
)
常见组合模式
模式 1:转换并验证
const processInput = flow(
S.trim,
O.fromPredicate(s => s.length > 0),
O.map(S.toLowerCase),
O.filter(isValidFormat)
)
模式 2:获取、转换、持久化
const syncUser = (id: number) =>
pipe(
fetchExternalUser(id),
TE.map(transformToInternalUser),
TE.flatMap(saveUser),
TE.map(user => ({ success: true, user }))
)
模式 3:并行执行并聚合
const fetchDashboardData = pipe(
TE.Do,
TE.apS('users', fetchUsers()),
TE.apS('orders', fetchOrders()),
TE.apS('metrics', fetchMetrics()),
TE.map(({ users, orders, metrics }) =>
buildDashboard(users, orders, metrics)
)
)
模式 4:顺序执行并提前退出
const processPayment = (paymentData: PaymentData) =>
pipe(
validatePayment(paymentData),
TE.flatMap(checkFunds),
TE.flatMap(reserveFunds),
TE.flatMap(processTransaction),
TE.flatMap(sendConfirmation)
)
模式 5:回退链
const getConfig = pipe(
getEnvConfig(),
O.alt(() => getFileConfig()),
O.alt(() => getDefaultConfig()),
O.getOrElse(() => hardcodedDefaults)
)
模式 6:条件分支
const processUser = (user: User) =>
pipe(
user,
O.fromPredicate(isAdmin),
O.match(
() => processRegularUser(user),
() => processAdminUser(user)
)
)
模式 7:累积结果
const processAll = (items: Item[]) =>
pipe(
items,
A.map(processItem),
A.separate, // Split into { left: errors[], right: successes[] }
({ left: errors, right: successes }) => ({
successes,
errors,
successRate: successes.length / items.length
})
)
类型推断提示
尽可能让 TypeScript 推断类型
// Good: Types flow through
const result = pipe(
users,
A.filter(u => u.active), // TypeScript knows u is User
A.map(u => u.name) // TypeScript knows result is string[]
)
// Only annotate when necessary
const processNumber = flow(
(n: number) => n * 2, // First function needs annotation
n => n + 1, // Rest are inferred
String
)
为公共 API 使用显式类型
// Good: Clear contract for public function
const processOrder: (order: Order) => E.Either<OrderError, ProcessedOrder> =
flow(
validateOrder,
E.flatMap(calculateTotals),
E.map(formatOrder)
)
性能注意事项
pipe 与 flow 的性能
pipe的开销极小,基本上只是函数调用flow会创建一个新函数,创建时有少量开销,但执行时没有- 对于值已知的热点路径,
pipe的速度略快 - 对于可复用函数,
flow可避免重复创建
避免不必要的中间数组
// Less efficient: Multiple array iterations
const result = pipe(
largeArray,
A.filter(predicate1),
A.filter(predicate2),
A.map(transform)
)
// More efficient: Combine predicates
const result = pipe(
largeArray,
A.filter(x => predicate1(x) && predicate2(x)),
A.map(transform)
)
// Or use filterMap for filter + map
const result = pipe(
largeArray,
A.filterMap(x =>
predicate1(x) && predicate2(x)
? O.some(transform(x))
: O.none
)
)
调试流水线
使用 tap 处理副作用
import { tap } from 'fp-ts/function'
const debugPipeline = pipe(
data,
tap(x => console.log('Step 1:', x)),
transform1,
tap(x => console.log('Step 2:', x)),
transform2
)
使用 trace 辅助函数
const trace = <A>(label: string) => (a: A): A => {
console.log(label, a)
return a
}
const result = pipe(
data,
trace('input'),
transform1,
trace('after transform1'),
transform2,
trace('final')
)
总结
| 使用场景 | 使用 pipe | 使用 flow |
|---|---|---|
| 立即转换一个值 | 是 | 否 |
| 创建可复用函数 | 否 | 是 |
| 作为回调传递 | 否 | 是 |
| 一次性转换 | 是 | 否 |
| 构建工具库 | 否 | 是 |
| fp-ts 操作链 | 是 | 两者皆可 |
请记住:
pipe(value, f, g)会立即执行flow(f, g)会返回一个供稍后使用的函数- 保持流水线步骤小巧且专注
- 提取具名函数以提高清晰度
- 使用 Do 记法处理复杂依赖
- 尽可能让 TypeScript 推断类型
评论
支持 Markdown