feat(flows): add RunConfig.groupFunctionResponsesInHistory to group function calls before responses#1330
Merged
Merged
Conversation
copybara-service
Bot
force-pushed
the
test_942009187
branch
7 times, most recently
from
5ea2a5f to
7d20914
Compare
…unction calls before responses RunConfig flag, off by default, that buffers function responses in the Contents request processor and flushes them after their function calls. When disabled (the default) responses stay paired with their call, preserving existing behavior. PiperOrigin-RevId: 943329408
copybara-service
Bot
force-pushed
the
test_942009187
branch
from
7d20914 to
1b9b395
Compare
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
1 participant
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.
feat(flows): add RunConfig.groupFunctionResponsesInHistory to group function calls before responses
RunConfig flag, off by default, that buffers function responses in the Contents
request processor and flushes them after their function calls. When disabled (the
default) responses stay paired with their call, preserving existing behavior.