Skip to content

Use {request,response}{s,stream} consistently #1320

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

glbrntt
Copy link
Collaborator

@glbrntt glbrntt commented Dec 3, 2021

Motivation:

Some of the new async-await APIs are inconsistent in their use of
'requests' vs 'requestStream' and 'responses' vs 'responseStream'. We
should name things consistently.

Modifications:

  • Rename 'requests' to 'requestStream' in generated server code
  • Rename 'responses' to 'responseStream' in client calls

Result:

More consistent naming.

@glbrntt glbrntt force-pushed the gb-async-naming-consistency branch 3 times, most recently from 24e68ea to 4bae2c5 Compare December 3, 2021 16:15
Motivation:

Some of the new async-await APIs are inconsistent in their use of
'requests' vs 'requestStream' and 'responses' vs 'responseStream'. We
should name things consistently.

Modifications:

- Rename 'requests' to 'requestStream' in generated server code
- Rename 'responses' to 'responseStream' in client calls

Result:

More consistent naming.
@glbrntt glbrntt force-pushed the gb-async-naming-consistency branch from 4bae2c5 to abb15a7 Compare December 6, 2021 17:59
@glbrntt glbrntt merged commit b0ee726 into grpc:1.6.0-async-await Dec 6, 2021
@glbrntt glbrntt deleted the gb-async-naming-consistency branch December 6, 2021 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants