googleapis / googleapis/gapic-generator-go
gapic: REGAPIC invocation mechanics should be streamlined
- Dominant language
- Go
- Stars
- 305
- Forks
- 60
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 13
Description
The request setup for REST clients needs to be streamlined and simplified. The existing code was OK to start, but the request construction logic should probably be abstracted into `gax-go`. [Example](https://github.com/googleapis/google-cloud-go/blob/f60bde45662a74b55fd58305891a7fa4e44e4bdd/alloydb/apiv1/alloydb_admin_client.go#L2042-L2094).
Contributor guide
Research direction
Start by inspecting the REST request construction at alloydb/apiv1/alloydb_admin_client.go lines 2042-2094, then compare it with the relevant gax-go request setup. Define the intended abstraction and its affected generated clients before changing anything; done means REGAPIC request mechanics are streamlined without losing existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100