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
Closes: https://github.com/unnoq/orpc/issues/709
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **New Features**
* Introduced a configurable ORPCModule for NestJS, enabling centralized
setup of error interceptors and event stream keep-alive intervals.
* Expanded main exports to include new configuration and lifecycle hooks
for greater flexibility.
* Added comprehensive documentation and usage examples for configuring
oRPC contracts in NestJS.
* **Bug Fixes**
* None.
* **Tests**
* Added new test case to verify integration and configuration of
ORPCModule within a NestJS application.
* **Chores**
* Updated build and TypeScript configurations to support experimental
decorators and improved build processes in both the core package and
playground.
* Updated playground scripts and dependencies for streamlined preview
and build.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
-**`interceptors`** - [Server-side client interceptors](/docs/client/server-side#lifecycle) for intercepting input, output, and errors.
248
+
-**`eventIteratorKeepAliveInterval`** - Keep-alive interval for event streams (see [Event Iterator Keep Alive](/docs/rpc-handler#event-iterator-keep-alive))
249
+
250
+
:::
251
+
223
252
## Create a Type-Safe Client
224
253
225
254
When you implement oRPC contracts in NestJS using `@orpc/nest`, the resulting API endpoints are OpenAPI compatible. This allows you to use an OpenAPI-compatible client link, such as [OpenAPILink](/docs/openapi/client/openapi-link), to interact with your API in a type-safe way.
0 commit comments