Hi George,
Can you recommend the appropriate application structure to take advantage of design view when using multiple repeater elements that are sourced from API calls?
The problem is that our data is coming from API calls, not static files, and therefore nothing is displayed when in design view. I have hired a Wappler development team and they tell me that it’s best to not use the design view and simply build directly via code and then view it in the browser. To me, that negates the real value of Wappler such that you should be able to view and easily edit the UI visually, otherwise we might as well be using VisualStudio!
One thought I had was to access test files when in design mode to view/edit the repeater structures, and then conditionally use the APIs when deployed, however the dev teams doesn’t think that’s a good solution…
I’m sure others must have run into these same issues when building apps that have many different repeater structures throughout that get populated via APIs… so, I thought you might be able to point me in the right direction to be able to gain the true benefit of the design view.
Thanks for your help!
James
Last updated: