You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each property of a entity is marked with a datatype in order to correctly save it to the database. This information is stored in a schema attribute of the class.
Currently, when configuring a list-view or a details-view, for each property, the component to display this property has to be named. Instead this information could be derived from the schema of the class. This should make the configuration file much smaller and less error-prone.
E.g.
Instead of writing
To achieve this, a connection between datatypes and components for entity-list and entity-details (form-component) needs to be defined.
In same cases (attendance, age) it has to be evaluated, whether a new datatype should be added or if the component information is still added through the config.
The text was updated successfully, but these errors were encountered:
see #764#552#180#826
EntitySchema holds information how an attribute can be displayed
EntitySchema holds information how an attribute can be edited
EntitySchemaDatatype provides a default component for displaying an data type
EntitySchemaDatatype provides a default component for editing an data type
EntityListComponent automatically fetches column information from schema if no other definition is found
FormComponent automatically fetches form field information from schema if no other definition is found
EntitySubrecord automatically fetches display and edit information from schema if no other definition is found
EntityList uses EntitySubrecord
Automatically create filters for properties using schema information
Update documentation
Automatically create (popup) form for entities -> Automatic PopUps #834
Each property of a entity is marked with a datatype in order to correctly save it to the database. This information is stored in a
schema
attribute of the class.Currently, when configuring a list-view or a details-view, for each property, the component to display this property has to be named. Instead this information could be derived from the schema of the class. This should make the configuration file much smaller and less error-prone.
E.g.
Instead of writing
Providing
name
is sufficient.To achieve this, a connection between datatypes and components for entity-list and entity-details (form-component) needs to be defined.
In same cases (attendance, age) it has to be evaluated, whether a new datatype should be added or if the component information is still added through the config.
The text was updated successfully, but these errors were encountered: