A modern programming language that makes developers happier.

kotlinlang

:wave: I wanted to start some discussion around <https://youtrack.jetbrains.com/issue/KT-52665|the deprecation of `ComponentRegistrar`>. <https://github.com/square/anvil|Anvil> currently relies on registering its extension first because of issues with KAPT (and potentially other extensions) short-circuiting and preventing later extensions from being executed (<https://youtrack.jetbrains.com/issue/KT-42103/AssertionError-Extension-to-be-removed-not-found-between-1.4.20-dev-3947-and-1.4.20-eap-23-resulting-in-compiler-errors|related ticket>). In the new `CompilerPluginRegistrar` API, there doesn't appear to be a way to register extensions with any ordering, which results in failures for Anvil since making sure we run before KAPT is critical. Is there a new equivalent API that can be used, or are there plans to add one for plugins that have ordering concerns?

Here's the relevant Anvil snippet where we register extension first: <https://github.com/square/anvil/blob/main/compiler/src/main/java/com/squareup/anvil/compiler/AnvilComponentRegistrar.kt#L82>
cc <@U0FCV4RND> <@U3M0FHPC0>

`CompilerPluginRegistrar` does not have ability to declare relation between extensions right now, but such API is planned <https://youtrack.jetbrains.com/issue/KT-55300|KT-55300>
For now you can continue to use `ComponentRegistrar`, it definitely won't be removed till K2 release (with proper plugin dependency mechanism)