You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BREAKING CHANGE: The `pipe()` function has been removed from the public API.
The direct API patterns provide better type inference:
- Parser merging: `positionals(options)` instead of `pipe(options, positionals)`
- Transforms: `map(parser, fn)` instead of `pipe(parser, map(fn))`
- Commands: `.command(name, parser, handler)` instead of `pipe(parser, handle(fn))`
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
The `pipe()` and `handle()` functions are exported for advanced use cases, but they're rarely needed with the standard API:
549
-
550
-
-**`pipe(a, b, c)`** - General function composition. Mostly superseded by direct parser merging (`positionals(options)`) and `map(parser, fn)`.
551
-
-**`handle(parser, fn)`** - Creates a `Command` from a parser and handler. Mostly superseded by `.command(name, parser, handler)`.
552
-
553
-
These exist for edge cases where you need to compose functions outside the fluent builder, but the main API covers most use cases with better type inference.
548
+
The `handle(parser, fn)` function is exported for advanced use cases where you need to create a `Command` object outside the fluent builder. It's mostly superseded by `.command(name, parser, handler)`.
0 commit comments