fix: Make FunctionResponses respect the order of FunctionCalls #671
+21
−16
Conversation
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
copybara-service
bot
force-pushed
the
test_845729296
branch
from
61a7723 to
44b98ef
Compare
Switched Flowable<Event> to Observable<Event> because it's immediately used as .toList(), so using Flowable<> brings no extra value. PiperOrigin-RevId: 845729296
copybara-service
bot
force-pushed
the
test_845729296
branch
from
44b98ef to
c5e704f
Compare
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.
fix: Make FunctionResponses respect the order of FunctionCalls
Switched Flowable to Observable because it's immediately used as .toList(), so using Flowable<> brings no extra value.