Understanding Gudhub

Field List

As we know from the items_list each data has its type. Thanks to this application knows what to do with any particular data. It uses special models to find out the right type. They do not have the same structure and sometimes can be difficult to understand. Despite differences, all these models are contained in field_list.

But at least there is an equal group of properties:

Name Type Description
data_model object describes data type settings; details...
data_type string unique text ID, which shows the field’s data type
field_id number unique ID in number format generated by the server
field_name string saves field name, could be written by the user
field_priority number shows the order in which display fields
name_space string unique field ID in text format which is an alternative to field_id for programming purposes; users can change it

data_model

Let’s talk about the most difficult part of field_list. All differences start here. data_model is a model that has a structure built by the programmer. It leads to complication code readability. But at the same time, it has base settings. One of them is interpretation, which should be in a model by default. Also, there is a group of data types that works with data:

use_default_value would determine whether the default value will be created. For its part, default_field_value contains exactly default value. multiple determines how many values will be in the field, the single one or more. As use_default_value, it is a boolean type. By the way, users can change their values.

interpretation

In keeping with its name, this property is responsible for interpretation data for the application. It is the base of the model. As usual, it contains only:

1. id

This string ID shows that type of interpretation is used for specific places (tables, form, etc.). It can be changed by the user.

2. settings

The object contains general settings of interpretation. Three of them are boolean type properties that determine the condition of the field: editable, show_field, show_field_name. In addition to these, the programmer can add his own settings.

3. src

The property shows for which location this interpretation was created. However, as stated above, there can be additional properties.