Another suggestion to complete the App Builder is to add an event for a page setting to set a local storage value from a parameter (and another action to delete that value). In this way, when send someone to a page, we can append a parameter to page, save that parameter to local storage and then we have a sort of “state” we can use for other events in the app builder. This is crucial when interacting without outside APIs and for keeping some sort of state as the person is navigating the app builder.
Thanks for the suggestion @ddsgad! I’ve shared it with the Application Builder team.
It would be great to have a persistent storage indeed. Not sure the local storage is the best candidate because it doesn’t play well with SSR but I’m sure we can find something.
Thanks.
Thanks. I didn’t realize that the actual Baserow is an SSR app. I thought it was partially client side. If SSR, then I guess you need to use cookies. That gets a bit more complicated.
Actually when you load the first page it’s generated by the server but then it’s only executed in the frontend, this is the best of all world because we can benefit from the good SEO of a regular website and the celerity of a single page app. However it comes with a few downside like the local storage access that can be tricky.
However it should totally work with cookie storage. We are probably just a bit more limited in space but that should be enough in our case.