Discuss: yaml parser currently allows short-cut values, which confuses users who
The yaml parser currently allows short-cut values, which confuses users who want to use the parser for data models. The short cuts make a certain sense however for users who create Records. How shall we proceed?
Examples
Using as value (correct):
prop:
datatype: INTEGER
A:
obligatory_properties:
prop: 3
Typo in data model (mistake only becomes apparent upon syncing with server):
A:
description: some RecordType
B:
obligatory_properties:
A: LIST<A>
Ideas
- Disallow or at least warn about the shortcuts.
- Allow the shortcuts only within
fixed_properties
. - Make the shortcuts configurable (default off, may be set to evaluate to value, datatype or description).
Edited by Daniel Hornung