Buffer extensibility
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
There are many different strategies that can be used to buffer data with many tradeoffs and niche use cases.
Right now the Buffer concept is relatively simple and rigid compared to Provider. We should consider introducing a trait that can express the role of a buffer and allow users to implement their own custom buffer types that can be used when building a workflow.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing Buffer and Provider concepts and tracing how a Buffer is used when building a workflow. Define what the proposed trait must express, how custom buffer types would integrate with workflow construction, and how completion would be verified; the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100