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
Plugins now have the ability to intercept and modify requests and
responses directly at the adapter level
### `Event Iterator Keep Alive`
We move configs for `Event Iterator Keep Alive` from `.handle` to
`handler options` (define when creating handler)
### Rename internal APIs
- `HandlerPlugin` -> `StandardHandlerPlugin`
- `ClientOptions` -> `FriendlyClientOptions`
- `ClientOptionsOut` -> `ClientOptions`
- `ClientPlugin` -> `StandardLinkPlugin`
- `StandardHandleOptions` -> `FriendlyStandardHandleOptions`
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Documentation**
- Clarified API descriptions, including keep-alive behavior and headers
for improved clarity.
- **Refactor**
- Streamlined internal handler implementations and standardized plugin
and configuration interfaces across client and server components.
- **Tests**
- Expanded test coverage for options resolution and plugin
initialization, while simplifying scenarios to focus on core
functionality.
- **Chores**
- Removed deprecated dependencies, updated package versions, and
consolidated module exports for a leaner codebase.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
To keep [Event Iterator](/docs/event-iterator) connections alive, `RPCHandler` periodically sends a ping comment to the client. You can configure this behavior using the following options:
78
78
@@ -81,7 +81,7 @@ To keep [Event Iterator](/docs/event-iterator) connections alive, `RPCHandler` p
81
81
-`eventIteratorKeepAliveComment` (default: `''`) – Custom content for ping comments.
0 commit comments