Software Flow

Last updated Sep 29, 2022

This goes over the general idea of how data flows through TASHelix.

When logging in for the first time, or when performing an update, the module configuration is pulled down from the server. These modules come in an old format used by the original TASHelix client. We transform this older model into a model that is quite similar, but is type-safe at compile time, and it has to go through SubappModelParser.parse() to do so.

What this function does is simply take the JSON object of the old model, and check that all expected properties both exist, and are the types that we expect. By extension, the subapp/region/item definition objects are designed in such a way that all optional attributes (not all types of subapps/regions/items will have all attributes) are composable, and that you must check for their existence before attempting to use them.