refactor(mlkit): extract ML Kit support into a dedicated mlkit module#240
Merged
Conversation
copybara-service
Bot
force-pushed
the
test_948831478
branch
4 times, most recently
from
July 22, 2026 08:21
751e008 to
b924987
Compare
Move the ML Kit GenAI prompt code, conversions, tracing, and tests out of the core module into a standalone mlkit module and wire it up in the Gradle and Blaze build. Change is backward compatible on code-level but it does require new artifact to be referenced during build time PiperOrigin-RevId: 951956680
copybara-service
Bot
force-pushed
the
test_948831478
branch
from
July 22, 2026 08:29
b924987 to
c465e1d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
refactor(mlkit): extract ML Kit support into a dedicated mlkit module
Move the ML Kit GenAI prompt code, conversions, tracing, and tests out of
the core module into a standalone mlkit module and wire it up in the Gradle
and Blaze build.
Change is backward compatible on code-level but it does require new artifact to be referenced during build time