GrpcStreamingRequestCall, GrpcStreamingResponseCall
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Kotlin
- Stars
- 4.4k
- Forks
- 627
- Avg merge
- 3d 15m
- Merged PRs (30d)
- 20
Description
Not having these was a stumbling block for implementing gRPC for one of our important users! It’s surprising that nothing happens until the request and response are sent.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the gRPC call API and the existing request and response call abstractions; the issue names the missing GrpcStreamingRequestCall and GrpcStreamingResponseCall types but gives no file or test entry point. Determine the expected streaming behavior and integration points, then define completion as working request and response streaming support with appropriate coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, kotlin
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100