Repository navigation
feat!: add a separate started handler for the consumer's /started - #27
Merged
Merged
Conversation
The consumer's /started no longer runs the start processor, which now serves only the provider's /start. A new WithStartedProcessor (DataFlowHandler) runs with the received DataAddress on the flow; the SDK then transitions to STARTED. A duplicate /started is acknowledged without invoking the handler. An address returned by a start processor can no longer replace the address a push consumer handed out at prepare. The signaling wire API is unchanged. BREAKING CHANGE: consumer logic for /started moves from WithStartProcessor to WithStartedProcessor; /started always ends in STARTED. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jimmarino
approved these changes
Nov 10, 2026
wolf4ood
approved these changes
Nov 10, 2026
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.
Splits the consumer's
/startedfrom the provider's/startprocessor, like the Java SDK'sOnStarted. The signaling wire API is unchanged (same endpoints, bodies and status codes; the HTTP tests pass unmodified).WithStartedProcessor(DataFlowHandler): runs on/startedwith the received DataAddress already on the flow; the SDK then transitions to STARTED.WithStartProcessornow only serves the provider's/start./startedis acknowledged without invoking the handler, like suspend/terminate/completed.Breaking (Go API only): consumer logic for
/startedmoves fromWithStartProcessortoWithStartedProcessor;/startedalways ends in STARTED.🤖 Generated with Claude Code