Multi-modules project : how to avoid public visibility for @Preview?

The documentation states that

The root module is the main module of your app that has a dependency on all other modules in the app. This is relevant because we generate the Showkase related classes in the package of the root module and we need to be able to access the UI elements across all the sub modules. This is only possible from the root module as it typically has a dependency on all the sub-modules.

• Does it mean that we can only have one @ShowkaseRootModule per project?

• Setting all the composables to render with a public visibility adds unnecessary items to the auto-completion list. Do you have an idea to help mitigate this?

Many thanks!

[borsini]

Thanks @iamutkarshtiwari , that would be an alternative. We ended up excluding our Previews from the IDE autocompletion-list.

Regarding my first question, does anyone have a clue? maybe @vinaygaba ? Having multiple ShowkaseRoot would help isolate previews and keep them internal

Does it mean that we can only have one @ShowkaseRootModule per project?

[vinaygaba]

Does it mean that we can only have one @ShowkaseRootModule per project?

ShowkaseRootModule are essentially meant to represent a collection previews based on the dependencies of the module where its declared. So in theory, it’s possible to have multiple ShowkaseRootModule in a project.