Bump epoxy from 4.6.2 to 5.0.0 #7264

dependabot · 2022-09-29T23:13:02Z

Bumps epoxy from 4.6.2 to 5.0.0.
Updates epoxy from 4.6.2 to 5.0.0

Release notes

5.0.0

This adds support for Kotlin Symbol Processing, while maintaining backwards compatibility with java annotation processing via the xprocessing library from Room.

This includes a major version bump to 5.0.0 because there may be slight behavior differences with KSP, especially for generic types in generated code. For example, if you previously had an epoxy attribute in java source code with a raw type it may now appear in the generated code with a wildcard type, which may require tweaking the type that is passed to the model.

Additionally, some type checking was improved, for example more accurate validation of proper equals and hashcode implementations.

To use Epoxy with KSP, simply apply it with the ksp gradle plugin instead of kapt (https://github.com/google/ksp/blob/main/docs/quickstart.md). See the new epoxy-kspsample module for an example.

Note that unfortunately the databinding processor does NOT support KSP, simply because Android databinding itself uses KAPT and KSP cannot currently depend on KAPT sources. The code changes are in place to enable KSP with databinding once the databinding plugin from Android supports KSP (although this is unlikely) - alternatively it may be possible to configure the KSP plugin to run after KAPT and depend on its outputs (you're on your own if you want to try that).

Also, parallel processing support was removed because it is not compatible with KSP.

We have also added easy interop with Jetpack Compose via functions in the epoxy-composeinterop artifact. See the epoxy-composesample module for example usage.

5.0.0-beta03

Fixes an empty list crash in the processor when a view with @ModelView extends a subclass that has a @ModelProp annotation with a default parameter value.

5.0.0-beta02

This adds support for Kotlin Symbol Processing, while maintaining backwards compatibility with java annotation processing via the xprocessing library from Room. Note that compilation speed with epoxy in KSP is not yet faster than KAPT due to some optimizations that remain to be made, but those should be made before long.

This includes a major version bump to 5.0.0 because there may be slight behavior differences with KSP, especially for generic types in generated code. For example, if you previously had an epoxy attribute in java source code with a raw type it may now appear in the generated code with a wildcard type, which may require tweaking the type that is passed to the model.

Additionally, some type checking was improved, for example more accurate validation of proper equals and hashcode implementations.

To use Epoxy with KSP, simply apply it with the ksp gradle plugin instead of kapt (https://github.com/google/ksp/blob/main/docs/quickstart.md). See the new epoxy-kspsample module for an example.

Note that unfortunately the databinding processor does NOT support KSP, simply because Android databinding itself uses KAPT and KSP cannot currently depend on KAPT sources. The code changes are in place to enable KSP with databinding once the databinding plugin from Android supports KSP (although this is unlikely) - alternatively it may be possible to configure the KSP plugin to run after KAPT and depend on its outputs (you're on your own if you want to try that).

Also, parallel processing support was removed because it is not compatible with KSP.

KSP Generated Sources in IDE

Note, that as of the current KSP version generated java sources are detected by the IDE but NOT generated kotlin sources. This means that generated epoxy kotlin extensions will not automatically be resolved in the IDE. You must manually configure your source sets to include ksp generated folders.

You can add this to your root build.gradle file to work around this
subprojects { project ->
    afterEvaluate {
        if (project.hasProperty("android")) {
            android {
                if (it instanceof com.android.build.gradle.LibraryExtension) {
                    libraryVariants.all { variant ->
                        def outputFolder = new File("build/generated/ksp/${variant.name}/kotlin")
                        variant.addJavaSourceFoldersToModel(outputFolder)
                        android.sourceSets.getAt(variant.name).java {
                            srcDir(outputFolder)
                        }
                    }
</tr></table> 

... (truncated)

Changelog

Sourced from epoxy's changelog.

5.0.0

This adds support for Kotlin Symbol Processing, while maintaining backwards compatibility with java annotation processing via the xprocessing library from Room.

This includes a major version bump to 5.0.0 because there may be slight behavior differences with KSP, especially for generic types in generated code. For example, if you previously had an epoxy attribute in java source code with a raw type it may now appear in the generated code with a wildcard type, which may require tweaking the type that is passed to the model.

Additionally, some type checking was improved, for example more accurate validation of proper equals and hashcode implementations.

To use Epoxy with KSP, simply apply it with the ksp gradle plugin instead of kapt (https://github.com/google/ksp/blob/main/docs/quickstart.md). See the new epoxy-kspsample module for an example.

Note that unfortunately the databinding processor does NOT support KSP, simply because Android databinding itself uses KAPT and KSP cannot currently depend on KAPT sources. The code changes are in place to enable KSP with databinding once the databinding plugin from Android supports KSP (although this is unlikely) - alternatively it may be possible to configure the KSP plugin to run after KAPT and depend on its outputs (you're on your own if you want to try that).

Also, parallel processing support was removed because it is not compatible with KSP.

We have also added easy interop with Jetpack Compose via functions in the epoxy-composeinterop artifact. See the epoxy-composesample module for example usage.

4.6.4 (September 23, 2021)

Clean up dependency for the experimental epoxy module

4.6.3 (September 11, 2021)

Add EpoxyModel#preBind hook(#1225)

Add unbind extension to ItemViewBindingEpoxyHolder (#1223)

Add missing loadStateFlow to PagingDataEpoxyController (#1209)

Commits

85f3cfc Prepare for release 5.0.0 (#1316)
aceb43b [ComposeInterop] Exposes Compose Epoxy Model generation (#1315)
0670dd3 [ComposeInterop] EpoxyInterop now handles @AfterPropSet ModelView methods (#1...
496d6b6 Upgrade Compose implementation to leverage perf improvements in the latest ch...
55c3b2e Update to latest kotlin/ksp/xprocessing (#1261)
8b3dd9c Add tag to ComposeEpoxyModel (#1288)
c2b9e39 Fix test output (#1279)
7825b76 [ModelView] - Add code to support set layout params manually from init (#1114)
e698c56 Change visibility of PagedListEpoxyController.modelCache (#1273)
205764d GitHub Actions (#1268)
Additional commits viewable in compare view

Updates epoxy-glide-preloading from 4.6.2 to 5.0.0

Release notes

Sourced from epoxy-glide-preloading's releases.

5.0.0

This adds support for Kotlin Symbol Processing, while maintaining backwards compatibility with java annotation processing via the xprocessing library from Room.

This includes a major version bump to 5.0.0 because there may be slight behavior differences with KSP, especially for generic types in generated code. For example, if you previously had an epoxy attribute in java source code with a raw type it may now appear in the generated code with a wildcard type, which may require tweaking the type that is passed to the model.

Additionally, some type checking was improved, for example more accurate validation of proper equals and hashcode implementations.

To use Epoxy with KSP, simply apply it with the ksp gradle plugin instead of kapt (https://github.com/google/ksp/blob/main/docs/quickstart.md). See the new epoxy-kspsample module for an example.

Note that unfortunately the databinding processor does NOT support KSP, simply because Android databinding itself uses KAPT and KSP cannot currently depend on KAPT sources. The code changes are in place to enable KSP with databinding once the databinding plugin from Android supports KSP (although this is unlikely) - alternatively it may be possible to configure the KSP plugin to run after KAPT and depend on its outputs (you're on your own if you want to try that).

Also, parallel processing support was removed because it is not compatible with KSP.

We have also added easy interop with Jetpack Compose via functions in the epoxy-composeinterop artifact. See the epoxy-composesample module for example usage.

5.0.0-beta03

Fixes an empty list crash in the processor when a view with @ModelView extends a subclass that has a @ModelProp annotation with a default parameter value.

5.0.0-beta02

This adds support for Kotlin Symbol Processing, while maintaining backwards compatibility with java annotation processing via the xprocessing library from Room. Note that compilation speed with epoxy in KSP is not yet faster than KAPT due to some optimizations that remain to be made, but those should be made before long.

This includes a major version bump to 5.0.0 because there may be slight behavior differences with KSP, especially for generic types in generated code. For example, if you previously had an epoxy attribute in java source code with a raw type it may now appear in the generated code with a wildcard type, which may require tweaking the type that is passed to the model.

Additionally, some type checking was improved, for example more accurate validation of proper equals and hashcode implementations.

To use Epoxy with KSP, simply apply it with the ksp gradle plugin instead of kapt (https://github.com/google/ksp/blob/main/docs/quickstart.md). See the new epoxy-kspsample module for an example.

Note that unfortunately the databinding processor does NOT support KSP, simply because Android databinding itself uses KAPT and KSP cannot currently depend on KAPT sources. The code changes are in place to enable KSP with databinding once the databinding plugin from Android supports KSP (although this is unlikely) - alternatively it may be possible to configure the KSP plugin to run after KAPT and depend on its outputs (you're on your own if you want to try that).

Also, parallel processing support was removed because it is not compatible with KSP.

KSP Generated Sources in IDE

Note, that as of the current KSP version generated java sources are detected by the IDE but NOT generated kotlin sources. This means that generated epoxy kotlin extensions will not automatically be resolved in the IDE. You must manually configure your source sets to include ksp generated folders.

You can add this to your root build.gradle file to work around this
subprojects { project ->
    afterEvaluate {
        if (project.hasProperty("android")) {
            android {
                if (it instanceof com.android.build.gradle.LibraryExtension) {
                    libraryVariants.all { variant ->
                        def outputFolder = new File("build/generated/ksp/${variant.name}/kotlin")
                        variant.addJavaSourceFoldersToModel(outputFolder)
                        android.sourceSets.getAt(variant.name).java {
                            srcDir(outputFolder)
                        }
                    }
</tr></table> 

... (truncated)

Changelog

Sourced from epoxy-glide-preloading's changelog.

5.0.0

This adds support for Kotlin Symbol Processing, while maintaining backwards compatibility with java annotation processing via the xprocessing library from Room.

This includes a major version bump to 5.0.0 because there may be slight behavior differences with KSP, especially for generic types in generated code. For example, if you previously had an epoxy attribute in java source code with a raw type it may now appear in the generated code with a wildcard type, which may require tweaking the type that is passed to the model.

Additionally, some type checking was improved, for example more accurate validation of proper equals and hashcode implementations.

To use Epoxy with KSP, simply apply it with the ksp gradle plugin instead of kapt (https://github.com/google/ksp/blob/main/docs/quickstart.md). See the new epoxy-kspsample module for an example.

Note that unfortunately the databinding processor does NOT support KSP, simply because Android databinding itself uses KAPT and KSP cannot currently depend on KAPT sources. The code changes are in place to enable KSP with databinding once the databinding plugin from Android supports KSP (although this is unlikely) - alternatively it may be possible to configure the KSP plugin to run after KAPT and depend on its outputs (you're on your own if you want to try that).

Also, parallel processing support was removed because it is not compatible with KSP.

We have also added easy interop with Jetpack Compose via functions in the epoxy-composeinterop artifact. See the epoxy-composesample module for example usage.

4.6.4 (September 23, 2021)

Clean up dependency for the experimental epoxy module

4.6.3 (September 11, 2021)

Add EpoxyModel#preBind hook(#1225)

Add unbind extension to ItemViewBindingEpoxyHolder (#1223)

Add missing loadStateFlow to PagingDataEpoxyController (#1209)

Commits

85f3cfc Prepare for release 5.0.0 (#1316)
aceb43b [ComposeInterop] Exposes Compose Epoxy Model generation (#1315)
0670dd3 [ComposeInterop] EpoxyInterop now handles @AfterPropSet ModelView methods (#1...
496d6b6 Upgrade Compose implementation to leverage perf improvements in the latest ch...
55c3b2e Update to latest kotlin/ksp/xprocessing (#1261)
8b3dd9c Add tag to ComposeEpoxyModel (#1288)
c2b9e39 Fix test output (#1279)
7825b76 [ModelView] - Add code to support set layout params manually from init (#1114)
e698c56 Change visibility of PagedListEpoxyController.modelCache (#1273)
205764d GitHub Actions (#1268)
Additional commits viewable in compare view

Updates epoxy-processor from 4.6.2 to 5.0.0

Release notes

Sourced from epoxy-processor's releases.

5.0.0

This adds support for Kotlin Symbol Processing, while maintaining backwards compatibility with java annotation processing via the xprocessing library from Room.

This includes a major version bump to 5.0.0 because there may be slight behavior differences with KSP, especially for generic types in generated code. For example, if you previously had an epoxy attribute in java source code with a raw type it may now appear in the generated code with a wildcard type, which may require tweaking the type that is passed to the model.

Additionally, some type checking was improved, for example more accurate validation of proper equals and hashcode implementations.

To use Epoxy with KSP, simply apply it with the ksp gradle plugin instead of kapt (https://github.com/google/ksp/blob/main/docs/quickstart.md). See the new epoxy-kspsample module for an example.

Note that unfortunately the databinding processor does NOT support KSP, simply because Android databinding itself uses KAPT and KSP cannot currently depend on KAPT sources. The code changes are in place to enable KSP with databinding once the databinding plugin from Android supports KSP (although this is unlikely) - alternatively it may be possible to configure the KSP plugin to run after KAPT and depend on its outputs (you're on your own if you want to try that).

Also, parallel processing support was removed because it is not compatible with KSP.

We have also added easy interop with Jetpack Compose via functions in the epoxy-composeinterop artifact. See the epoxy-composesample module for example usage.

5.0.0-beta03

Fixes an empty list crash in the processor when a view with @ModelView extends a subclass that has a @ModelProp annotation with a default parameter value.

5.0.0-beta02

This adds support for Kotlin Symbol Processing, while maintaining backwards compatibility with java annotation processing via the xprocessing library from Room. Note that compilation speed with epoxy in KSP is not yet faster than KAPT due to some optimizations that remain to be made, but those should be made before long.

This includes a major version bump to 5.0.0 because there may be slight behavior differences with KSP, especially for generic types in generated code. For example, if you previously had an epoxy attribute in java source code with a raw type it may now appear in the generated code with a wildcard type, which may require tweaking the type that is passed to the model.

Additionally, some type checking was improved, for example more accurate validation of proper equals and hashcode implementations.

To use Epoxy with KSP, simply apply it with the ksp gradle plugin instead of kapt (https://github.com/google/ksp/blob/main/docs/quickstart.md). See the new epoxy-kspsample module for an example.

Note that unfortunately the databinding processor does NOT support KSP, simply because Android databinding itself uses KAPT and KSP cannot currently depend on KAPT sources. The code changes are in place to enable KSP with databinding once the databinding plugin from Android supports KSP (although this is unlikely) - alternatively it may be possible to configure the KSP plugin to run after KAPT and depend on its outputs (you're on your own if you want to try that).

Also, parallel processing support was removed because it is not compatible with KSP.

KSP Generated Sources in IDE

Note, that as of the current KSP version generated java sources are detected by the IDE but NOT generated kotlin sources. This means that generated epoxy kotlin extensions will not automatically be resolved in the IDE. You must manually configure your source sets to include ksp generated folders.

You can add this to your root build.gradle file to work around this
subprojects { project ->
    afterEvaluate {
        if (project.hasProperty("android")) {
            android {
                if (it instanceof com.android.build.gradle.LibraryExtension) {
                    libraryVariants.all { variant ->
                        def outputFolder = new File("build/generated/ksp/${variant.name}/kotlin")
                        variant.addJavaSourceFoldersToModel(outputFolder)
                        android.sourceSets.getAt(variant.name).java {
                            srcDir(outputFolder)
                        }
                    }
</tr></table> 

... (truncated)

Changelog

Sourced from epoxy-processor's changelog.

5.0.0

This adds support for Kotlin Symbol Processing, while maintaining backwards compatibility with java annotation processing via the xprocessing library from Room.

This includes a major version bump to 5.0.0 because there may be slight behavior differences with KSP, especially for generic types in generated code. For example, if you previously had an epoxy attribute in java source code with a raw type it may now appear in the generated code with a wildcard type, which may require tweaking the type that is passed to the model.

Additionally, some type checking was improved, for example more accurate validation of proper equals and hashcode implementations.

To use Epoxy with KSP, simply apply it with the ksp gradle plugin instead of kapt (https://github.com/google/ksp/blob/main/docs/quickstart.md). See the new epoxy-kspsample module for an example.

Note that unfortunately the databinding processor does NOT support KSP, simply because Android databinding itself uses KAPT and KSP cannot currently depend on KAPT sources. The code changes are in place to enable KSP with databinding once the databinding plugin from Android supports KSP (although this is unlikely) - alternatively it may be possible to configure the KSP plugin to run after KAPT and depend on its outputs (you're on your own if you want to try that).

Also, parallel processing support was removed because it is not compatible with KSP.

We have also added easy interop with Jetpack Compose via functions in the epoxy-composeinterop artifact. See the epoxy-composesample module for example usage.

4.6.4 (September 23, 2021)

Clean up dependency for the experimental epoxy module

4.6.3 (September 11, 2021)

Add EpoxyModel#preBind hook(#1225)

Add unbind extension to ItemViewBindingEpoxyHolder (#1223)

Add missing loadStateFlow to PagingDataEpoxyController (#1209)

Commits

85f3cfc Prepare for release 5.0.0 (#1316)
aceb43b [ComposeInterop] Exposes Compose Epoxy Model generation (#1315)
0670dd3 [ComposeInterop] EpoxyInterop now handles @AfterPropSet ModelView methods (#1...
496d6b6 Upgrade Compose implementation to leverage perf improvements in the latest ch...
55c3b2e Update to latest kotlin/ksp/xprocessing (#1261)
8b3dd9c Add tag to ComposeEpoxyModel (#1288)
c2b9e39 Fix test output (#1279)
7825b76 [ModelView] - Add code to support set layout params manually from init (#1114)
e698c56 Change visibility of PagedListEpoxyController.modelCache (#1273)
205764d GitHub Actions (#1268)
Additional commits viewable in compare view

Updates epoxy-paging from 4.6.2 to 5.0.0

Release notes

Sourced from epoxy-paging's releases.

5.0.0

This adds support for Kotlin Symbol Processing, while maintaining backwards compatibility with java annotation processing via the xprocessing library from Room.

This includes a major version bump to 5.0.0 because there may be slight behavior differences with KSP, especially for generic types in generated code. For example, if you previously had an epoxy attribute in java source code with a raw type it may now appear in the generated code with a wildcard type, which may require tweaking the type that is passed to the model.

Additionally, some type checking was improved, for example more accurate validation of proper equals and hashcode implementations.

To use Epoxy with KSP, simply apply it with the ksp gradle plugin instead of kapt (https://github.com/google/ksp/blob/main/docs/quickstart.md). See the new epoxy-kspsample module for an example.

Note that unfortunately the databinding processor does NOT support KSP, simply because Android databinding itself uses KAPT and KSP cannot currently depend on KAPT sources. The code changes are in place to enable KSP with databinding once the databinding plugin from Android supports KSP (although this is unlikely) - alternatively it may be possible to configure the KSP plugin to run after KAPT and depend on its outputs (you're on your own if you want to try that).

Also, parallel processing support was removed because it is not compatible with KSP.

We have also added easy interop with Jetpack Compose via functions in the epoxy-composeinterop artifact. See the epoxy-composesample module for example usage.

5.0.0-beta03

Fixes an empty list crash in the processor when a view with @ModelView extends a subclass that has a @ModelProp annotation with a default parameter value.

5.0.0-beta02

This adds support for Kotlin Symbol Processing, while maintaining backwards compatibility with java annotation processing via the xprocessing library from Room. Note that compilation speed with epoxy in KSP is not yet faster than KAPT due to some optimizations that remain to be made, but those should be made before long.

This includes a major version bump to 5.0.0 because there may be slight behavior differences with KSP, especially for generic types in generated code. For example, if you previously had an epoxy attribute in java source code with a raw type it may now appear in the generated code with a wildcard type, which may require tweaking the type that is passed to the model.

Additionally, some type checking was improved, for example more accurate validation of proper equals and hashcode implementations.

To use Epoxy with KSP, simply apply it with the ksp gradle plugin instead of kapt (https://github.com/google/ksp/blob/main/docs/quickstart.md). See the new epoxy-kspsample module for an example.

Note that unfortunately the databinding processor does NOT support KSP, simply because Android databinding itself uses KAPT and KSP cannot currently depend on KAPT sources. The code changes are in place to enable KSP with databinding once the databinding plugin from Android supports KSP (although this is unlikely) - alternatively it may be possible to configure the KSP plugin to run after KAPT and depend on its outputs (you're on your own if you want to try that).

Also, parallel processing support was removed because it is not compatible with KSP.

KSP Generated Sources in IDE

Note, that as of the current KSP version generated java sources are detected by the IDE but NOT generated kotlin sources. This means that generated epoxy kotlin extensions will not automatically be resolved in the IDE. You must manually configure your source sets to include ksp generated folders.

You can add this to your root build.gradle file to work around this
subprojects { project ->
    afterEvaluate {
        if (project.hasProperty("android")) {
            android {
                if (it instanceof com.android.build.gradle.LibraryExtension) {
                    libraryVariants.all { variant ->
                        def outputFolder = new File("build/generated/ksp/${variant.name}/kotlin")
                        variant.addJavaSourceFoldersToModel(outputFolder)
                        android.sourceSets.getAt(variant.name).java {
                            srcDir(outputFolder)
                        }
                    }
</tr></table> 

... (truncated)

Changelog

Sourced from epoxy-paging's changelog.

5.0.0

This adds support for Kotlin Symbol Processing, while maintaining backwards compatibility with java annotation processing via the xprocessing library from Room.

This includes a major version bump to 5.0.0 because there may be slight behavior differences with KSP, especially for generic types in generated code. For example, if you previously had an epoxy attribute in java source code with a raw type it may now appear in the generated code with a wildcard type, which may require tweaking the type that is passed to the model.

Additionally, some type checking was improved, for example more accurate validation of proper equals and hashcode implementations.

To use Epoxy with KSP, simply apply it with the ksp gradle plugin instead of kapt (https://github.com/google/ksp/blob/main/docs/quickstart.md). See the new epoxy-kspsample module for an example.

Note that unfortunately the databinding processor does NOT support KSP, simply because Android databinding itself uses KAPT and KSP cannot currently depend on KAPT sources. The code changes are in place to enable KSP with databinding once the databinding plugin from Android supports KSP (although this is unlikely) - alternatively it may be possible to configure the KSP plugin to run after KAPT and depend on its outputs (you're on your own if you want to try that).

Also, parallel processing support was removed because it is not compatible with KSP.

We have also added easy interop with Jetpack Compose via functions in the epoxy-composeinterop artifact. See the epoxy-composesample module for example usage.

4.6.4 (September 23, 2021)

Clean up dependency for the experimental epoxy module

4.6.3 (September 11, 2021)

Add EpoxyModel#preBind hook(#1225)

Add unbind extension to ItemViewBindingEpoxyHolder (#1223)

Add missing loadStateFlow to PagingDataEpoxyController (#1209)

Commits

85f3cfc Prepare for release 5.0.0 (#1316)
aceb43b [ComposeInterop] Exposes Compose Epoxy Model generation (#1315)
0670dd3 [ComposeInterop] EpoxyInterop now handles @AfterPropSet ModelView methods (#1...
496d6b6 Upgrade Compose implementation to leverage perf improvements in the latest ch...
55c3b2e Update to latest kotlin/ksp/xprocessing (#1261)
8b3dd9c Add tag to ComposeEpoxyModel (#1288)
c2b9e39 Fix test output (#1279)
7825b76 [ModelView] - Add code to support set layout params manually from init (#1114)
e698c56 Change visibility of PagedListEpoxyController.modelCache (#1273)
205764d GitHub Actions (#1268)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps `epoxy` from 4.6.2 to 5.0.0. Updates `epoxy` from 4.6.2 to 5.0.0 - [Release notes](https://github.com/airbnb/epoxy/releases) - [Changelog](https://github.com/airbnb/epoxy/blob/master/CHANGELOG.md) - [Commits](airbnb/epoxy@4.6.2...5.0.0) Updates `epoxy-glide-preloading` from 4.6.2 to 5.0.0 - [Release notes](https://github.com/airbnb/epoxy/releases) - [Changelog](https://github.com/airbnb/epoxy/blob/master/CHANGELOG.md) - [Commits](airbnb/epoxy@4.6.2...5.0.0) Updates `epoxy-processor` from 4.6.2 to 5.0.0 - [Release notes](https://github.com/airbnb/epoxy/releases) - [Changelog](https://github.com/airbnb/epoxy/blob/master/CHANGELOG.md) - [Commits](airbnb/epoxy@4.6.2...5.0.0) Updates `epoxy-paging` from 4.6.2 to 5.0.0 - [Release notes](https://github.com/airbnb/epoxy/releases) - [Changelog](https://github.com/airbnb/epoxy/blob/master/CHANGELOG.md) - [Commits](airbnb/epoxy@4.6.2...5.0.0) --- updated-dependencies: - dependency-name: com.airbnb.android:epoxy dependency-type: direct:production update-type: version-update:semver-major - dependency-name: com.airbnb.android:epoxy-glide-preloading dependency-type: direct:production update-type: version-update:semver-major - dependency-name: com.airbnb.android:epoxy-processor dependency-type: direct:production update-type: version-update:semver-major - dependency-name: com.airbnb.android:epoxy-paging dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>

…r code completion) Ref: https://github.com/airbnb/epoxy/releases/tag/5.0.0beta02

Fix error `error: annotation type not applicable to this kind of declaration`

bmarty · 2022-10-03T14:58:23Z

@jmartinesp I have enabled KSP, and made the induced required changes. Smoke test on the app is fine to me.
Can you review and approve? Then we will merge the PR, but after the next RC.

ElementBot · 2022-10-03T15:38:54Z

	Warnings
⚠️	vector/build.gradle#L323 - A newer version of org.jetbrains.kotlin:kotlin-reflect than 1.7.10 is available: 1.7.20
⚠️	vector/build.gradle#L323 - A newer version of org.jetbrains.kotlin:kotlin-reflect than 1.7.10 is available: 1.7.20
⚠️	vector/src/main/java/im/vector/app/features/home/room/detail/timeline/item/MessageVoiceItem.kt#L111 - Custom view `AudioWaveformView` has `setOnTouchListener` called on it but does not override `performClick`
⚠️	vector/src/main/java/im/vector/app/features/home/room/detail/timeline/item/MessageVoiceItem.kt#L111 - Custom view `AudioWaveformView` has `setOnTouchListener` called on it but does not override `performClick`
⚠️	vector/src/main/java/im/vector/app/features/home/room/detail/timeline/item/MessageVoiceItem.kt#L111 - `onTouch` lambda should call `View#performClick` when a click is detected
⚠️	vector/src/main/java/im/vector/app/features/home/room/detail/timeline/item/MessageVoiceItem.kt#L111 - `onTouch` lambda should call `View#performClick` when a click is detected

Generated by 🚫 dangerJS against 8653b74

jmartinesp

LGTM too.

sonarqubecloud · 2022-10-03T21:11:14Z

SonarCloud Quality Gate failed.

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
9.5% Duplication

dependencies.gradle

dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Sep 29, 2022

dependabot bot requested review from a team and jmartinesp and removed request for a team September 29, 2022 23:13

jmartinesp and others added 7 commits September 30, 2022 09:39

Fix dependencies and code issues

f5cb980

Restore validateEpoxyModelUsage annotation processing arg

570bc57

Enable Ksp for Epoxy Processor

cba920f

Workaround to have KSP generated Kotlin code available in the IDE (fo…

9f68d9d

…r code completion) Ref: https://github.com/airbnb/epoxy/releases/tag/5.0.0beta02

Fix issue with expected types.

8e375a7

Remove usage of @JvmField in Epoxy Items.

24fe677

Fix error `error: annotation type not applicable to this kind of declaration`

Naming convention: Epoxy item classes have Itemsuffix

e282380

bmarty added the Z-Merge After Release label Oct 3, 2022

Prefer to add explicit group.

8653b74

jmartinesp mentioned this pull request Oct 3, 2022

Element Android crashing with custom poll event. #7270

Closed

jmartinesp approved these changes Oct 3, 2022

View reviewed changes

jmartinesp enabled auto-merge (squash) October 3, 2022 15:43

jmartinesp disabled auto-merge October 3, 2022 15:43

Merge branch 'develop' into dependabot/gradle/epoxy-5.0.0

cde088e

bmarty reviewed Oct 5, 2022

View reviewed changes

dependencies.gradle Outdated Show resolved Hide resolved

Fix bad merge conflict fix

27e408f

bmarty merged commit 6d2caf6 into develop Oct 5, 2022

bmarty deleted the dependabot/gradle/epoxy-5.0.0 branch October 5, 2022 15:30

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump epoxy from 4.6.2 to 5.0.0 #7264

Bump epoxy from 4.6.2 to 5.0.0 #7264

dependabot bot commented on behalf of github Sep 29, 2022

bmarty commented Oct 3, 2022

ElementBot commented Oct 3, 2022

jmartinesp left a comment

sonarqubecloud bot commented Oct 3, 2022

Bump epoxy from 4.6.2 to 5.0.0 #7264

Bump epoxy from 4.6.2 to 5.0.0 #7264

Conversation

dependabot bot commented on behalf of github Sep 29, 2022

5.0.0

5.0.0-beta03

5.0.0-beta02

KSP Generated Sources in IDE

5.0.0

4.6.4 (September 23, 2021)

4.6.3 (September 11, 2021)

5.0.0

5.0.0-beta03

5.0.0-beta02

KSP Generated Sources in IDE

5.0.0

4.6.4 (September 23, 2021)

4.6.3 (September 11, 2021)

5.0.0

5.0.0-beta03

5.0.0-beta02

KSP Generated Sources in IDE

5.0.0

4.6.4 (September 23, 2021)

4.6.3 (September 11, 2021)

5.0.0

5.0.0-beta03

5.0.0-beta02

KSP Generated Sources in IDE

5.0.0

4.6.4 (September 23, 2021)

4.6.3 (September 11, 2021)

bmarty commented Oct 3, 2022

ElementBot commented Oct 3, 2022

jmartinesp left a comment

Choose a reason for hiding this comment

sonarqubecloud bot commented Oct 3, 2022