DF-25178: Adds custom subscription handling for EA specific implementations#807
Merged
Merged
Conversation
Contributor
NPM Publishing labels 🏷️🟢 This PR has valid version labels and will cause a |
bcc3e71 to
440c591
Compare
alejoberardino
previously approved these changes
Jun 8, 2026
mmcallister-cll
approved these changes
Jun 9, 2026
Contributor
|
🚀 Successfully created version bump PR: #822 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a
customSubscriptionMessagesbuilder toWebSocketTransportso EAs can fully control how subscribe/unsubscribe WebSocket messages are built each background-execute cycle. This replaces the earlierbatchSubscribeMessage/batchUnsubscribeMessageAPI with a more flexible hook that receives full subscription deltas (new,stale, anddesired).WebSocketCustomBuilderswithcustomSubscriptionMessages(context, subscriptions) => unknown[]subscriptionMessageBuilder; per-subscriptionsubscribeMessage/unsubscribeMessagebuilders continue to work via a default adaptersendMessagesto accept a single ordered message arrayMotivation (DF-25178): Some providers need EA-specific subscription logic—e.g. batching multiple feeds into one message, custom ordering, or provider-specific payload shapes—that the fixed per-feed and batch-builder APIs could not express cleanly.
Backward compatibility: Existing adapters using
subscribeMessage/unsubscribeMessageare unchanged. Only adapters that adoptcustomSubscriptionMessagesneed updates.API
Configure either per-subscription builders or the custom builder, not both: