Add Stream-based Control Flow for Observation Emitter #5
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 commit introduces tokio streams to control how often a third-party
adapter is called to fetch data from a data source. The adapter is called
on an interval using a timer, and the results are chunked before being
returned as a stream.
It adds a simple stream-based pipeline to gather observations
as they're emitted by a local cache. It plumbs together a futures API
to make event handling nature and easy.
chore: Add stream-based control flow for third-party adapters.