Enables the creation of a datastructure "globals" in the page instance.
Here we can store variable information and then refer to it dynamically in our VueElements that compose our web page.
It works in a similar fashion as the "data" of a vue instance. It gives us the ability to define data in our page instance, in our server side, instead of relying on javascript to define auxiliary datastructures inside elements.
Examples of usage:
Loading state
All Elements "disabled" prop are binded to "globals.loading_state", mimicking a loading state.
Keeping context
In a mapping view, I need to keep the context of the selected taxonomy and this info is not stored in any visual element, i can do this by setting a "globals.selected_taxonomy".
Easy rendering
Mimics the data of a Vue Application and thus can be used to bind to "v-model" cases. The rendering of a stepper relies on defining the v-model the keeps the step state. This can be achieved by defining in server side a "globals.stepState".
Enables the creation of a datastructure "globals" in the page instance. Here we can store variable information and then refer to it dynamically in our VueElements that compose our web page.
It works in a similar fashion as the "data" of a vue instance. It gives us the ability to define data in our page instance, in our server side, instead of relying on javascript to define auxiliary datastructures inside elements.
Examples of usage:
Loading state All Elements "disabled" prop are binded to "globals.loading_state", mimicking a loading state.
Keeping context In a mapping view, I need to keep the context of the selected taxonomy and this info is not stored in any visual element, i can do this by setting a "globals.selected_taxonomy".
Easy rendering Mimics the data of a Vue Application and thus can be used to bind to "v-model" cases. The rendering of a stepper relies on defining the v-model the keeps the step state. This can be achieved by defining in server side a "globals.stepState".