#106894Site settings do not support storage of subkeys, if the dot-seprated setting exists as a key.
Description
Arbitrary keys like `foo.bar` and `foo.bar.baz` exclude each other, since they can not be expressed as a yaml tree.
Given the following settings.definitions.yaml
settings:
foo.bar:
type: string
default: ''
label: FooBar
foo.bar.baz:
type: string
default: ''
label: FooBarBaz
</code>
There is no way to store both in settings.yaml:
foo:
bar: 'value'
foo:
# overwrites the assignment to `foo.bar`
bar:
baz: 'value'
Note: TypoScript constants allowed this, since TypoScript can store value and childrens per node (since it represents the children with a dot attached)
Reviews 7
- 14.3 96989[BUGFIX] Stop probing settings once the tree is empty
- main 96605[BUGFIX] Stop probing settings once the tree is empty
- main 95438[!!!][WIP][TASK] Remove legacy tree based site settings
- 13.4 90723[BUGFIX] Fix site settings yaml-dump of specific settings
- main 90284[BUGFIX] Fix site settings yaml-dump of specific settings
- main 89738[BUGFIX] Store and process site settings.yaml as a map
- 13.4 89711[BUGFIX] Store and process site settings.yaml as a map