ngg opened a new issue, #7875:
URL: https://github.com/apache/opendal/issues/7875
### Describe the bug
`dav-server-opendalfs` depends on `opendal` without `default-features =
false`, so downstream projects get OpenDAL’s default features enabled even when
they intentionally disable them.
This is a problem for projects that use a custom OpenDAL feature set, for
example using `http-transport-reqwest-native-tls` instead of the default HTTP
transport.
### Steps to Reproduce
1. Create a project that depends on `dav-server-opendalfs`.
2. Also depend on `opendal` with `default-features = false` and a custom
feature set, such as native-tls HTTP transport.
3. Run `cargo tree -e features`.
4. Observe that OpenDAL default features are still enabled through
`dav-server-opendalfs`.
### Expected Behavior
`dav-server-opendalfs` should not force OpenDAL default features on
downstream users. It should depend only on what it needs, for example
`opendal-core`, or use `opendal` with `default-features = false` and explicit
features.
### Additional Context
The integration itself only needs core OpenDAL types for its library code.
Tests can keep using the `opendal` facade with explicit service features.
### Are you willing to submit a PR to fix this bug?
- [x] Yes, I would like to submit a PR.
--
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]
