-
Notifications
You must be signed in to change notification settings - Fork 3
IfElse
Nightinggale edited this page Jun 8, 2018
·
1 revision
Has two operations where it executes one of them based on the result of a test operation.
If you have two ways to patch a file and you need to pick one based on some test condition, you can use IfElse to avoid having to test twice.
| Tag | Mandatory | Type | Default | Description |
|---|---|---|---|---|
| patchName | no | string | Name of patch for log/profiling | |
| test | yes | operation | Operation used for test condition | |
| passed | yes | operation | Runs this is test is true | |
| failed | yes | operation | Runs this is test is false | |
| passInnerTest | no | bool | true | See pass conditions |
Note: while each operation is a single operation, they can be of any type of operation, including Sequence, AND, OR and IfElse. In other words each of the operations can be expanded as needed with no limit on complexity.
The success of the IfElse copies the result from passed or failed, depending on which is executed.
The success of the IfElse copies the result from the test operation.
<li Class="ModCheck.IfElse">
<test Class = "ModCheck.LoadOrder>
<!-- some test conditions -->
</test>
<passed Class="something">
<!-- some patching -->
</passed>
<failed Class="something else">
<!-- different patching -->
</failed>
</li>