Ive been curious about this and just read this chat. I was thinking since they are id i needed to keep them unique.
However i imagine i could use this as a way to share what data should be accessible between parts of my app.
At the moment, I’ve been defining everything on each page/partial, because id dint want to clutter my layout with data.
With this, could i more define common meta data sections query params/state managers and such on the content page and then the partials that will be used on this content page, just have same app id as content page and wappler will show meta data from content page.
Ill test this later, just in middle of something. But would this also be able to share what server connect should be accessible? example in partial get datapicker that references server connect in content page?
Edit: Query params and managers are all good. sadly doesn’t show the server connect on parent page.
Just an idea, it would be huge for me, is there any way to get datapick to give options from content pages?
Like could it be something where a few other ids could be used just for meta data, example data id, this will have datapicker show all possible data with pages/partials with the same data id?
Does that make sense?
Because my current method is i always just manually have to look at parent element to get see how its structured. or new way I’m doing is just setting up a dev server connect on the partial, setup exactly the same, so i can reference it that way in datapicker, and then just i just make sure to rename from scSomethingDev to scSomething, so it references the content page server connect.
Edit Edit: Another benefit for me is i could just place all the data i need in the content page, and then all ui in partials. Just to me would be extremely good for organisation and atleast how my brain thinks haha