You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sprintf('Template for "%s" only partially applied. Please check the newly created nodes beneath %s.', $node->getNodeType()->getLabel(), (string)$node),
? sprintf('Template for "%s" only partially applied. Please check the newly created nodes beneath %s.', $node->getNodeType()->getLabel(), (string)$node)
96
-
: sprintf('Template for "%s" was not applied. Only %s was created.', $node->getNodeType()->getLabel(), (string)$node);
Copy file name to clipboardExpand all lines: README.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -182,21 +182,20 @@ way around.
182
182
183
183
## Exception handling, resuming with the next possible operation.
184
184
185
-
In the first step the configuration is evaluated, all Runtime Exceptions (for example caused in an EEL Expression) are caught, and any malformed parts of the template are ignored (with their errors being logged).
186
-
This might lead to a partially evaluated template with some properties or childNodes missing.
185
+
In the first step the configuration is processed, exceptions like those caused by an EEL Expression are caught, and any malformed parts of the template are ignored (with their errors being logged).
186
+
This might lead to a partially processed template with some properties or childNodes missing.
187
187
188
-
You can decide via the exception handling strategy `continueWithPartiallyEvaluatedTemplate`, if you want to apply this partially evaluated template `true` or abort the process `false` which will only lead to creating the root node as if there was no template.
189
-
190
-
The setting is configurable via Settings.yaml in `Flowpack.NodeTemplates.continueWithPartiallyEvaluatedTemplate` it defaults to `true`.
188
+
You can decide via the exception handling configuration `Flowpack.NodeTemplates.exceptionHandling`, if you want to start the node creation of this partially processed template (`stopOnException: false`) or abort the process (`stopOnException: true`), which will only lead to creating the root node, ignoring the whole template.
191
189
192
190
```yaml
193
191
Flowpack:
194
192
NodeTemplates:
195
-
exceptionHandlingStrategy:
196
-
continueWithPartiallyEvaluatedTemplate: true
193
+
exceptionHandling:
194
+
templateConfigurationProcessing:
195
+
stopOnException: false
197
196
```
198
197
199
-
In case exceptions are thrown while applying the template like because a node constraint was not met or the `type` field was not set the creation of the childNode is aborted, but we continue with applying the other left over parts of the template.
198
+
In case exceptions are thrown in the node creation of the template, because a node constraint was not met or the `type` field was not set, the creation of the childNode is aborted, but we continue with the node creation of the other left over parts of the template.
200
199
It behaves similar with properties: In case a property value doesn't match its declared type the exception is logged, but we will try to continue with the next property.
0 commit comments