idea: Make `list` required to return `content-length`
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 825
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 127
Description
OpenDAL previously handled returning `content-length` in the `list` response as a best-effort approach. We encouraged users to call `stat` outside of `list`. However, this approach has placed a significant burden on our users. Perhaps we should make it mandatory for `list` to return `content-length` and update our implementations accordingly. This way, our users won't be confused by this behavior anymore.
Contributor guide
Research direction
Review the existing list response contract and how storage implementations currently provide content-length, using the issue’s contrast with stat as the starting point. Define the mandatory behavior and update affected implementations; done means list consistently returns content-length without requiring a separate stat call.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100