new feature: support content_language in opendal::metadata and opendal:capability
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 825
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 127
Description
### Feature Description
support content_language in opendal::options::WriteOptions
### Problem and Solution
comment on https://github.com/apache/opendal/pull/6468#discussion_r2249120305
not support content_language in opendal::options::WriteOptions
### Additional Context
_No response_
### Are you willing to contribute to the development of this feature?
- [x] Yes, I am willing to contribute to the development of this feature.
Contributor guide
Research direction
Start at opendal::options::WriteOptions and trace the related metadata and capability entry points; review the linked pull request discussion for the expected content_language behavior. Done means content_language is supported consistently in WriteOptions, metadata, and capability as described by the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100