ANDROID-16934 -- (IV) Remove databinding related code #482
Conversation
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
- Remove databinding feature and kapt (used by first one) - Replace implementation by "api" in "androidx.compose.ui" library
|
[Firebase] 📱 New catalog for testing generated: |
dhonti-axpe
requested review from
a team,
dnieto-r,
jeslat and
juangardi21
and removed request for
a team
jeslat
approved these changes
Jan 15, 2026
dnieto-r
approved these changes
Jan 15, 2026
dhonti-axpe
merged commit 7e9c463
into
ANDROID-16934/base-remove-databinding
4 checks passed
This was referenced Jan 19, 2026
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.
🎟️ Jira ticket
ANDROID-16934
🥅 What's the goal?
After applying following previous PRs:
Is fully remove DataBinding usage from the Mística library and align its Gradle configuration with the new Jetpack Compose–based architecture, ensuring proper dependency propagation to consumer projects (
android-messengerandSmartWifi).🚧 How do we do it?
The implementation has been carried out following these steps:
databinding-feature:* Databinding is no longer used by any component in the library.
kotlin-kaptplugin:* This plugin was only required for Databinding and other annotation processors that are no longer part of the library. Removing it simplifies the Gradle setup and reduces build overhead.
implementation "androidx.compose.ui:ui:$compose_ui_version"is replaced by:
api "androidx.compose.ui:ui:$compose_ui_version"Due to Compose is part of Mistica's public API. Declaring it as api ensure the dependency is correctly propagated to consumer projects and prevents compilation issues
☑️ Checks
🧪 How can I test this?
As is mentioned in the corresponding ANDROID-16934 ticket, is tested in the "android-messenger" client project that the total PR changes exposed in #476 works correctly.