PsiACE opened a new pull request, #7:
URL: https://github.com/apache/opendal-oli/pull/7
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements. You can link an issue to this PR using the GitHub syntax. For
example `Closes #123` indicates that this PR will close issue #123.
-->
Closes #2 .
# Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
`oli cp` previously uploaded every object as `application/octet-stream`,
which breaks consumers relying on MIME
metadata. This closes the gap reported in #2 by letting users pin a type
explicitly while defaulting to
OpenDAL’s existing MIME guessing.
# What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
- Enable OpenDAL’s `MimeGuessLayer` for every operator built from oli
configs so files get sensible defaults
automatically.
- Add a `--content-type` flag to `oli cp` and thread it through both
single-file and recursive code paths.
- Update CLI/help docs and integration snapshots to reflect the new output.
- Add unit tests covering the flag parsing and the MimeGuess behavior.
# Are there any user-facing changes?
Yes: `oli cp` now accepts `--content-type`, the inferred MIME is printed by
oli stat, and the README explains
how to override the type when necessary
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!---
If there are any breaking changes to public APIs, please add the
`breaking-changes` label.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
