11..index ::
22 single: Config; Defining and processing configuration values
33
4- Defining andprocessing configuration values
4+ Defining andProcessing Configuration Values
55============================================
66
7- Validatingconfiguration values
7+ ValidatingConfiguration Values
88-------------------------------
99
1010After loading configuration values from all kinds of resources, the values
@@ -38,7 +38,7 @@ they are when first encountered. Also, some keys are only available when
3838another key has a specific value (in the sample configuration above: the
3939``memory `` key only makes sense when the ``driver `` is ``sqlite ``).
4040
41- Defining ahierarchy ofconfiguration values using the TreeBuilder
41+ Defining aHierarchy ofConfiguration Values Using the TreeBuilder
4242------------------------------------------------------------------
4343
4444All the rules concerning configuration values can be defined using the
@@ -66,10 +66,10 @@ should be returned from a custom ``Configuration`` class which implements the
6666 }
6767 }
6868
69- Addingnode definitions to thetree
69+ AddingNode Definitions to theTree
7070-----------------------------------
7171
72- Variablenodes
72+ VariableNodes
7373~~~~~~~~~~~~~~
7474
7575A tree contains node definitions which can be laid out in a semantic way.
@@ -91,7 +91,7 @@ The root node itself is an array node, and has children, like the boolean
9191node ``auto_connect `` and the scalar node ``default_connection ``. In general:
9292after defining a node, a call to ``end() `` takes you one step up in the hierarchy.
9393
94- Nodetype
94+ NodeType
9595~~~~~~~~~
9696
9797It is possible to validate the type of a provided value by using the appropriate
@@ -108,7 +108,7 @@ node definition. Node type are available for:
108108and are created with ``node($name, $type) `` or their associated shortcut
109109``xxxxNode($name) `` method.
110110
111- Numericnode constraints
111+ NumericNode Constraints
112112~~~~~~~~~~~~~~~~~~~~~~~~
113113
114114..versionadded ::2.2
@@ -133,7 +133,7 @@ allowing to validate the value::
133133 ->end()
134134 ;
135135
136- Enumnodes
136+ EnumNodes
137137~~~~~~~~~~
138138
139139..versionadded ::2.1
@@ -152,7 +152,7 @@ values::
152152
153153This will restrict the ``gender `` option to be either ``male `` or ``female ``.
154154
155- Arraynodes
155+ ArrayNodes
156156~~~~~~~~~~~
157157
158158It is possible to add a deeper level to the hierarchy, by adding an array
@@ -193,7 +193,7 @@ inside the current node. According to the prototype definition in the example
193193above, it is possible to have multiple connection arrays (containing a ``driver ``,
194194``host ``, etc.).
195195
196- Arraynode options
196+ ArrayNode Options
197197~~~~~~~~~~~~~~~~~~
198198
199199Before defining the children of an array node, you can provide options like:
@@ -236,7 +236,7 @@ In XML, each ``parameters`` node would have a ``name`` attribute (along with
236236the final array. The ``useAttributeAsKey `` is useful for normalizing how
237237arrays are specified between different formats like XML and YAML.
238238
239- Default and requiredvalues
239+ Default and requiredValues
240240---------------------------
241241
242242For all node types, it is possible to define default values and replacement
@@ -316,7 +316,7 @@ you can take advantage of the shortcut
316316The ``canBeDisabled `` method looks about the same except that the section
317317would be enabled by default.
318318
319- Mergingoptions
319+ MergingOptions
320320---------------
321321
322322Extra options concerning the merge process may be provided. For arrays:
@@ -330,7 +330,7 @@ For all nodes:
330330``cannotBeOverwritten() ``
331331 don’t let other configuration arrays overwrite an existing value for this node
332332
333- Appendingsections
333+ AppendingSections
334334------------------
335335
336336If you have a complex configuration to validate then the tree can grow to
@@ -502,7 +502,7 @@ By changing a string value into an associative array with ``name`` as the key::
502502 ->end()
503503 ;
504504
505- Validationrules
505+ ValidationRules
506506----------------
507507
508508More advanced validation rules can be provided using the
@@ -548,7 +548,7 @@ Usually, "then" is a closure. Its return value will be used as a new value
548548for the node, instead
549549of the node's original value.
550550
551- Processingconfiguration values
551+ ProcessingConfiguration Values
552552-------------------------------
553553
554554The:class: `Symfony\\ Component\\ Config\\ Definition\\ Processor ` uses the tree