Skip to content
Snippets Groups Projects
Commit f20c9f28 authored by Henrik tom Wörden's avatar Henrik tom Wörden
Browse files

Merge branch 'f-reuse-yaml-doc' into 'dev'

FIX: if multiple updates for one entity exist, the retrieve would result in an...

See merge request !57
parents bd19f0ee 7fa244c8
No related branches found
No related tags found
2 merge requests!107Release v0.11.0,!57FIX: if multiple updates for one entity exist, the retrieve would result in an...
Pipeline #51052 passed
......@@ -86,6 +86,41 @@ list of previously defined names of Properties and/or RecordTypes. Note that if
recommended_properties:
Author:
Reusing Properties
==================
Properties defined once (either as a property of a Record or as a separate Property) can be reused
later in the yaml file. That requires that after the first occurrence of the property, the
attributes have to be empty. Otherwise the reuse of the property would be conflicting with its
original definition.
Example:
--------
.. code-block:: yaml
Project:
obligatory_properties:
projectId:
datatype: INTEGER
description: 'UID of this project'
date:
datetype: DATETIME
description: Date of a project or an experiment
Experiment:
obligatory_properties:
experimentId:
datatype: INTEGER
description: 'UID of this experiment'
date: # no further attributes here, since property was defined above in 'Project'!
The above example defines two Records: Project and Experiment
The property ``date`` is defined upon its first occurrence as a property of ``Project``.
Later, the same property is also added to ``Experiment`` where no additional attributes are
allowed to specify.
Datatypes
=========
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment