FIX: Accept Iterable of Mappings from async step functions in functional API #25
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.
This Pull Request introduces an enhancement to the Fluxus library's functional API, specifically targeting the
step
function and related classes within theconduit
module. The changes expand the range of acceptable return types for functions passed tostep
, allowing for greater flexibility in asynchronous programming patterns.Key Changes:
Expanded Awaitable Return Types:
step
function and theStep
class have been extended to includeAwaitable[Iterable[Mapping[str, Any]]]
andAwaitable[AsyncIterable[Mapping[str, Any]]]
. This allows asynchronious functions passed tostep
to return not just single mappings/dictionaries but also iterables or async iterables of mappings/dictionaries.Handling Awaitable Iterables:
Step
class implementation to properly handle and unwrap the new awaitable iterable return types. This ensures that the library can asynchronously process iterables of mappings/dictionaries.Closes #24.