fix(grpc-sdk): make chat sendMessage files optional at SDK boundary#1548
Merged
Merged
Conversation
ChrisPdgn
marked this pull request as draft
July 9, 2026 10:39
ChrisPdgn
marked this pull request as ready for review
July 9, 2026 10:43
Expose SendMessageInput with optional files and normalize via SendMessageRequest.fromPartial so existing callers are not broken by ts-proto's required repeated-field typing. Co-authored-by: Cursor <cursoragent@cursor.com>
ChrisPdgn
force-pushed
the
fix/v0.16-chat-sendmessage-optional-files
branch
from
July 9, 2026 11:37
334319b to
207d780
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
2 participants
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.
Expose SendMessageInput with optional files and normalize via SendMessageRequest.fromPartial so existing callers are not broken by ts-proto's required repeated-field typing.
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
The PR fulfills these requirements:
mainbranchfix #xxx, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: