Given the sophistication of the new multipage apps, is it possible to convert an existing module to a page (with all the component tree and code exposed and editable) rather than it being embedded as a module that has to be edited separately? The current implementation of 'duplicate to multipage' for a module just duplicates the full module. I realise this would need some manual intervention to connect missing module input and outputs but that would be a small price to pay for the superior performance of the multipage apps.
Alternatively, is there a way of making a module an app without laboriously copying and pasting all the code and components? Some sort of 'clone module to app' functionality?
I do not believe we currently have plans yet for module->page of a multipage app or for module -> app but I can definitely make a feature request for both of these features
We are currently roadmapping out modules v2 which will give the feature a face lift so we love getting as much feedback on how we can improve modules.
When you mention that 'duplicate to multipage' for a module currently duplicates the full module, are you saying you don't want the full module but only sub-components inside of a module to be selectable?
For the time being, we highly recommend building out functionality in apps, with modules being more reserved for very simple logic that needs to be duplicated and consistent across apps(such as headers, footers, etc.) with apps being much easier to combine together with multipage apps for more complex logic/user interaction.
