As I am making more modules I find myself having to refresh the app's page to see the new ones in the list. There is also some debugging of the module when you first use it in an app so also have ot refresh the app's page to get the newest changes.
How about a refresh button that reloads the newest and newest versions of the modules.
While I am here how about the same thing for global settings like JS and CSS.
Iām experiencing a similar issue where I need to refresh tables to see new modules and updates. It would be much more efficient if there was a way to reference a query in the main app directly from the module. Additionally, having an option to refresh the entire state would also solve my case.
Has anyone found a solution or workaround for this? Any tips on handling the inputs of the modules effectively would be greatly appreciated as well.
Currently there is not a work around and most people use hard refreshes, but I am making a feature request for a more modular and quicker refresh to make building out with modules smoother!
Also, could you elaborate more on 'reference a query in the main app directly from the module' ?
Recently, the Retool team activated the Multi-page beta feature, which solves this challenge and more.
From my experience, it seems I was using Modules instead of Pages.
Modules appear to be designed for reusable elements rather than being integral parts of the application. Will continue exploring modules from diffrent perspective.
Yes multipage is super useful and handles a ton of use cases.
Modules are much more niche and are more bug prone. Often times used for things such as boilerplate headers/footers or really simple queries that are transferrable.
We just rolled out multipage to cloud beta customers yesterday. As we work through testing and getting it set for a general launch, there should be more information coming out soon on our website.
Super excited about this feature, stay tuned for more news on it and the release date via our website/emails!