The loose field definition is a shorthand for the strict version, and follows the following example form:
fields: { name: 'text', age: 'int', }
In this form, the key is the field name, and the value is the type of the scalar field.
If you need to define a field with a more complex type (i.e., for maps, sets, lists), you must use the strict field definition.
Plus, while it still provides autocomplete, the loose field definition does not statically enforce the type of the field, whereas the strict field definition does.
Overview
The loose field definition is a shorthand for the strict version, and follows the following example form:
In this form, the key is the field name, and the value is the type of the scalar field.
If you need to define a field with a more complex type (i.e., for maps, sets, lists), you must use the strict field definition.
Plus, while it still provides autocomplete, the loose field definition does not statically enforce the type of the field, whereas the strict field definition does.