Condition

Conditions are expressions that evaluates to either true or false. The location of the condition decides its purpose in the ZSPEC. When placed in a data path, it helps in filtering the records to narrow down the data to your desired . In the other locations, it serves as a mere conditional statement.

Possible Locations

• Data Path
• Property @condition-for-request
• Property @condition-for-response
• Property @condition-for-all
• Property @value-condition
• Argument @condition
• Error @condition

Syntaxes of a Condition

    

        
copy
        

            

        
    
    

         

<left-operand> <relational-operator> <right-operand> // for simple conditions


    

    

        
copy
        

            

        
    
    

         

<left-operand> <relational-operator> <right-operand> <relational-operator> <left-operand> <relational-operator> <right-operand> // for complex conditions


    

Left and Right Operands

The operands are the building blocks of a condition and our ZSPEC supports versatile operand choices. Learning about these operand choices will help in constructing conditions that accurately reflect your intended constraints.

Here are the available left and right operands:

• Static data: You can utilize static keys or values.
• Dynamic data: Employ the data path when you want to use a dynamic data.

Relational Operators

Relational Operators in conditions are symbols used to compare values and determine logical relationship between them. They are crucial in creating expressions that evaluate to true or false.

Following is a set of relational operators that you can use in ZSPEC,

Samples

Let us have a common JSON body in the data manager for applying all these expressions and operand choices.

{
    "trips": [
        {
            "trip_name": "London - Emily Jones",
            "trip_id": "5545984000000006873",
            "no_of_days": 10,
            "travelers": [
                {
                    "traveler_name":[
                        "Ms",
                        "Emily",
                        "Jones"
                    ],
                    "traveler_email": "emily@qke.com"
                }
            ],
            "destination": "Westminster Abbey"
        }
    ]
}

Using static data

Following is a condition with static data from the above JSON body.

trip_name ~~ 'London*' 

Here are the details of this condition,

• Left operand - A static key from the JSON body.
• Operator - Like. In this condition, it serves the starts with comparison.
• Right operand - A known value.

Using Dynamic data

Consider that we need to verify whether the values of the ’traveler_email’ key match the values of the ’email’ key from another resource named ’travelers’. In this scenario, we are accessing the dynamic values from a different resource. So, the condition should be expressed like this,

traveler_email :: travelers:$.email

Following are the condition details,

• Left operand - A static key from the JSON body.
• Operator - in
• Right operand - Here, the value is dynamic and accessed from a different resource using data path.

Check here to learn more about constructing data path.

Relational Operators

We will see a few samples of how you can use the operators in constructing conditions.