tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity

Clarify how Only and Except rules combine

Browse Source
This commit is contained in:
Hamish Friedlander 2013-07-02 13:54:06 +12:00
parent 5484283a25
commit df218d76da
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/en/topics/configuration.md
View File

@ -227,8 +227,8 @@ To accommodate this, value sections can be filtered to only be used when either
current environment.
To achieve this you add a key to the related header section, either "Only" when the value section should be included
only when the rules contained match, or "Except" when the value section should be included except when the rules
contained match.
only when all the rules contained match, or "Except" when the value section should be included except when all of the
rules contained match.
You then list any of the following rules as sub-keys, with informational values as either a single value or a list.
@ -256,6 +256,12 @@ For instance, to add a property to "foo" when a module exists, and "bar" otherwi
property: 'bar'
---
Note than when you have more than one rule for a nested fragment, they're joined like
FRAGMENT_INCLUDED = (ONLY && ONLY) && !(EXCEPT && EXCEPT)
That is, the fragment will be included if all Only rules match, except if all Except rules match
### The values
The values section of YAML configuration files is quite simple - it is simply a nested key / value pair structure