[BREAKING] rename StripeStreamResponseAsync
's .read()
to read_async()
for consistency
#1474
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why?
We added a linter ages ago to enforce that all async functions have the
_async
suffix. This consistency ensures that users are properlyawait
ing them (failure to do so can be the source of tricky bugs).There was one exception to that rule, which I'm removing here.
While it's a breaking change for 100% of users, it will be a loud one. The method is renamed and they'll get both typecheck and runtime failures when they use the old method. Also, it only affects a single user-facing method.
This was the one method in our codebase that didn't comply with the convention, so it's being updated
What?
StripeStreamResponseAsync.read()
toStripeStreamResponseAsync.read_async()
See Also
async
functions are namedX_async
#1326Changelog
StripeStreamResponseAsync.read()
to.read_async()
async
usage.Quote.pdf_async().read()
method. A typechecker will alert you to this change.