feat: Convert many toReadableSequentialData to toPbjReader
- Dominant language
- Java
- Stars
- 44
- Forks
- 15
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 12
Description
Closes out remaining spots (gRPC client `PbjGrpcCall`, generated `ServiceGenerator` dispatch, `Codec.parse(Bytes)`/`parseStrict(Bytes)`) still using `Bytes.toReadableSequentialData()`, switching them to `Bytes.toPbjReader()`.
**Benefit:** finishes the migration so the whole call chain benefits from the buffer-reuse path, not just Codec internals.
PR: hashgraph/pbj#918
Contributor guide
Research direction
Review PbjGrpcCall, the generated ServiceGenerator dispatch, and Codec.parse(Bytes)/parseStrict(Bytes), focusing on their remaining use of Bytes.toReadableSequentialData(). Done means those listed call sites use Bytes.toPbjReader() and the migration is complete; the issue references PR hashgraph/pbj#918.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java
- Domain
- backend-api-design, devtools, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 30/100