[Feature request] Listener/interceptor functionality on GrpcClient
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 4.4k
- Forks
- 627
- Avg merge
- 3d 15m
- Merged PRs (30d)
- 20
Description
There is no way to listen to all calls made on GrpcClient . Only low level interceptors on OkHttp client are possible.
A listener should report method name and deserialized message. That would make debugging easier and enable creating a plugin for flipper
flipper-grpc-plugin was made for grpc-java implementation.
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 at GrpcClient and review how the existing low-level OkHttp interceptors observe calls. Define a listener that reports the method name and deserialized message, with support for the Flipper plugin use case; done means callers can observe all GrpcClient calls with that information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100