Tracking issues for migrating C bindings to RFC-6213 Options API
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 825
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 127
Description
Following RFC-6213 (https://github.com/apache/opendal/pull/6213), OpenDAL has introduced a new options-based API pattern to replace the builder pattern for operations (e.g. write_with().append(true)). The new approach simplifies cross language binding parity for capabilities and supported options across all language bindings!
The following Options need to be added or migrated to use this new API in the C bindings:
- [ ] WriteOptions: (partially added)
- [ ] ReadOptions (not implemented)
- [ ] StatOptions (not implemented)
- [ ] DeleteOptions (not implemented)
- [ ] ListOptions (not implemented)
Contributor guide
Research direction
Start with RFC-6213 and the partially added WriteOptions implementation in the C bindings. Review the listed ReadOptions, StatOptions, DeleteOptions, and ListOptions work, then confirm that each uses the new options-based API pattern rather than the builder pattern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100