docs: use async for
instead of for
for streaming FastAPI resp
#570
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.
Hi 👋🏻
I tried the docs snippet and found that it should use
async for
instead offor
to avoidTypeError: 'async_generator' object is not iterable
Summary:
This PR updates the
fastapi.md
documentation to useasync for
instead offor
when iterating over an async generator in thegenerate
function within theextract
function.Key points:
fastapi.md
documentation filefor
loop toasync for
ingenerate
function withinextract
functionTypeError
when iterating overusers
, which is an async generatorGenerated with ❤️ by ellipsis.dev