Sahil-Shadwal opened a new pull request, #7029: URL: https://github.com/apache/opendal/pull/7029
# 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 #6920 Tracking issue: #6829 # 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. --> This PR splits the seafile service out of `core` into its own crate `opendal-service-seafile` as part of the core-split effort (RFC-6828). This modularizes the codebase and allows for better dependency management. # 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. --> - Moved [seafile](cci:1://file:///Users/sahilshadwal/Desktop/opendal/core/services/seafile/src/lib.rs:33:0-36:1) service code from `core/src/services/seafile` to new crate at `core/services/seafile`. - Created `core/services/seafile/Cargo.toml` with necessary dependencies. - Updated `core/Cargo.toml` to add `opendal-service-seafile` to the workspace and dependencies. - Updated `core/src/lib.rs` to re-export the `seafile` service. - Updated `opendal-core` to remove the old `seafile` module and feature flags. # Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> No. The public API and behavior remain unchanged as the service is re-exported from the wrapper crate. <!--- 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]
