Parameters
Parsing prefix keywords
There is 2 allowed parsing prefix keywords:
input
: corresponding to the input_data
.
output
: corresponding to the result output data (returned by the apply_rules()
method).
Here are examples:
input.name
: maps to input_data["name"]
.
output.check_admission.is_admitted
: maps to result["check_admission"]["is_admitted"]
.
They both can be used in condition and action parameters.
Info
A value without any prefix keyword is a constant.
Parsing error
Raise by default
By default, errors during condition and action parameters parsing are raised.
If we refer to the dictionary example:
| rules = {
"check_admission": {
"ADMITTED_RULE": {
"condition": lambda power: power in ["strength", "fly", "immortality"],
"condition_parameters": {"power": "input.super_power"},
"action": set_admission,
"action_parameters": {"value": True},
},
"DEFAULT_RULE": {
"condition": None,
"condition_parameters": None,
"action": set_admission,
"action_parameters": {"value": False},
},
}
}
|
With modified data like:
| input_data = {
"id": 1,
"name": "Superman",
"civilian_name": "Clark Kent",
"age": None,
"city": "Metropolis",
"language": "french",
"power": "fly",
"favorite_meal": "Spinach",
"secret_weakness": "Kryptonite",
"weapons": [],
}
|
By default we will get a KeyError
exception during the execution of the apply_rules()
method because of power
vs super_power
.
Ignore
You can change the by default raising behavior of the parameter's parsing.
Two ways are possible:
- At the configuration level: impacts all the parameters.
- At the parameter's level.
Configuration level
You just have to add the following key somewhere in your configuration:
| ---
rules:
default_rule_set:
check_admission:
ADMITTED_RULE:
condition: HAS_SCHOOL_AUTHORIZED_POWER
action: set_admission
action_parameters:
value: true
DEFAULT_RULE:
condition: null
action: set_admission
action_parameters:
value: false
conditions:
HAS_SCHOOL_AUTHORIZED_POWER:
description: "Does applicant have a school authorized power?"
validation_function: has_authorized_super_power
condition_parameters:
power: input.super_power
conditions_source_modules:
- my_folder.conditions
actions_source_modules:
- my_folder.actions
parsing_error_strategy: ignore #
|
It will affect all the parameters.
Parameter level
Quick Sum Up
input.super_power?
: set the value to None
input.super_power?no_power
: set the value to no_power
input.super_power!
: force raise exception (case when ignore is set by default)
You can also handle more precisely that aspect at parameter's level:
| ---
rules:
default_rule_set:
check_admission:
ADMITTED_RULE:
condition: HAS_SCHOOL_AUTHORIZED_POWER
action: set_admission
action_parameters:
value: true
DEFAULT_RULE:
condition: null
action: set_admission
action_parameters:
value: false
conditions:
HAS_SCHOOL_AUTHORIZED_POWER:
description: "Does applicant have a school authorized power?"
validation_function: has_authorized_super_power
condition_parameters:
power: input.super_power? #
conditions_source_modules:
- my_folder.conditions
actions_source_modules:
- my_folder.actions
|
Info
You can enforce raising exceptions at parameter's level with !
.
| power: input.super_power!
|
Default value (parameter level)
Finally, you can set a default value at parameter's level. This value will be used if there is an exception during parsing:
| ---
rules:
default_rule_set:
check_admission:
ADMITTED_RULE:
condition: HAS_SCHOOL_AUTHORIZED_POWER
action: set_admission
action_parameters:
value: true
DEFAULT_RULE:
condition: null
action: set_admission
action_parameters:
value: false
conditions:
HAS_SCHOOL_AUTHORIZED_POWER:
description: "Does applicant have a school authorized power?"
validation_function: has_authorized_super_power
condition_parameters:
power: input.super_power?no_power #
conditions_source_modules:
- my_folder.conditions
actions_source_modules:
- my_folder.actions
|
Good to know
Parameter's level is overriding configuration level.