As we are continuing to develop and add new features to our Losant Experiences, our backend team is left wondering what are the limits to stuffing more JSON data into what I think is called the context?
It is what gets exposed as pageData when you have the Render Page node in a workflow.
An example of this is that for a device navigation bar, on the left column, we adjusted our devices to nest based on a hierarchy we have. So we end up with something like…
locations: 9 elements
Thats some pseudo code of course, but we end up with several companies, each having their own arrays of locations, sublocations, assets and finally sensors, all devices in the dashboard.
Then we throw another json object containing all events. Then maybe we throw another device list in there because sometimes a flat device list is easier to traverse/search than the nested one we used for the nav.
Collapsed, it looks like:
but once expanded all out, it is quite large.
And this is the point of my question. Its been easy so far to just make everything available to all pages.
Do we need to be more targeted about what each page receives in its pageData?
Will we ever hit a limit of too much data, or does it just begin to slow things down the larger that pageData gets?
Sample Screenshot to give context to what I am talking about, in actuality we have flows that put more objects into pageData than what is shown here: