manchangfengxu opened a new pull request, #6868: URL: https://github.com/apache/opendal/pull/6868
This commit extracts the moka service into its own crate, `opendal-service-moka`, following the established service splitting pattern. The changes primarily involve moving the source files and updating Cargo configurations accordingly. # Which issue does this PR close? Part of #6829. This PR completes the task for the moka service. <!-- 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. --> # Rationale for this change This change is part of the ongoing effort to modularize OpenDAL services as outlined in RFC-6828. By splitting the `moka` service into its own crate, we reduce the complexity and compile times of `opendal-core` for users who do not need this specific service. <!-- 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. --> # What changes are included in this PR? - Created the new crate `opendal-service-moka` under `core/services/`. - Migrated all `moka` service source code from `opendal-core` to the new crate. - Updated `Cargo.toml` configurations to reflect the new workspace member, dependency, and feature flag. - Ensured the `moka` service is still exposed through the `opendal` facade crate to maintain API compatibility. <!-- 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. --> # Are there any user-facing changes? No, this is a refactoring. <!-- 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]
