PluginGroupConfiguration,PluginGroup,Plugin missed in no.op

[serhiiLiubetskyiI]

Describe the bug
PluginGroupConfiguration,PluginGroup,Plugin missed in no.op

To Reproduce
Steps to reproduce the behavior:

1. Setup no.op for prod build variant
   "prodApi"(libs.plutolib.plugins.bundle.core.no.op)
   "prodApi"(libs.plutolib.pluto.no.op)

2. Create class with plugins
   class DataSourcePluginGroup : PluginGroup("datasource-group") {
   override fun getConfig() = PluginGroupConfiguration(
   name = "DataSource Group"
   )

   override fun getPlugins(): List {
   return listOf(
   PlutoSharePreferencesPlugin(),
   PlutoDatastorePreferencesPlugin(),
   PlutoRoomsDatabasePlugin()
   )
   }
   }

3. Add plugin groupe in Pluto
   Pluto.Installer(this)
   .addPlugin(PlutoLoggerPlugin())
   .addPlugin(PlutoNetworkPlugin())
   .addPlugin(PlutoExceptionsPlugin())
   //.addPlugin(PlutoLayoutInspectorPlugin())
   .addPluginGroup(DataSourcePluginGroup())
   .install()

Expected behavior
build variant with no.op should works

[srtvprateek]

this is happening coz plugin module does not have no-op version, as it did not need it.
the fix for the above issue is to keep your PluginGroup file in variant folder (can refer to the sample app).

let me know if you face any issue in this.

[serhiiLiubetskyiI]

Hi, I keep it in variantfolder but it is not comfortable)

…

On Wed, 29 Nov 2023, 07:06 Prateek, ***@***.***> wrote: this is happening coz plugin module does not have no-op version, as it did not need it. the fix for the above issue is to keep your PluginGroup file in variant folder (can refer to the sample app). let me know if you face any issue in this. — Reply to this email directly, view it on GitHub <#293 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BCTUBZ5AMFHZ2WHMROG3DOTYG27GLAVCNFSM6AAAAAA7WO2JHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZRGIZTAMZRGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>