Fixed
Status Update
No update yet.
Comments
au...@google.com
au...@google.com
this would be nice but given Compose and all other priorities, we are not planning to make any big investments in data binding (support KSP is a very big task).
au...@google.com
Makes sense. And is there any way to trigger data binding without kapt plugin, assuming there are no custom binding adapters in given module?
[Deleted User] <[Deleted User]>
unfortunately no. data binding still needs to be able to read your code and annotation processing is the only API that allows us to do it :(
la...@gmail.com
It's a very disappointing decision for many projects who heavily depend on data binding, which will never be able to get rid of all bindings code and especially rewrite all UI to Compose.
It means that bindings are essentially deprecated
Description
com.android.support:design:26.0.0
| | +--- com.android.support:multidex:1.0.1
| | +--- com.android.support:support-v4:26.0.0 (*)
| | +--- com.android.support:appcompat-v7:26.0.0
| | | +--- com.android.support:support-annotations:26.0.0
| | | +--- com.android.support:support-v4:26.0.0 (*)
| | | +--- com.android.support:support-vector-drawable:26.0.0
| | | | +--- com.android.support:support-annotations:26.0.0
| | | | \--- com.android.support:support-compat:26.0.0 (*)
| | | \--- com.android.support:animated-vector-drawable:26.0.0
| | | +--- com.android.support:support-vector-drawable:26.0.0 (*)
| | | \--- com.android.support:support-core-ui:26.0.0 (*)
com.android.support:multidex:1.0.1 should not be included in the design support library.