Explicit events are raised in the rule postlude with a raise statement. You can raise events from a postlude like so:
The event name is given by the
<expr>. The expression is evaluated and the resulting string is used as the event name.
Because the event name is an expression, you must use a string rather than using a bare word.
attributes clause allows the developer to add event attributes to the event. The expression that follows the
attributes key word must evaluate to a map. The keys and values in the map will be used as event attributes. This is particularly useful when you want to pass through all, or most, of the attributes that the current rule received:
This raises the event
explicit:foo with all of the attributes that were passed into the enclosing rule.
You can control which rulesets see an explicit event using the optional
The for clause is followed by an expression that is evaluated to determine which rule sets should see the event. The result must be a string, giving the target ruleset ID or an array of target rulesets. At the moment, the system will use the version of the current ruleset.
In the Sky Event API, explicit events will be raised to any ruleset that an entity has installed unless a
for clause is present. You can specify the current ruleset using
meta:rid from the meta library.
Like any other postlude statement, explicit events can be guarded:
The event in the preceding example will only be raised if the variable flipper has the value "two".
Explicit events allow KRL programmers to chain rules together. Rule chaining is good for modularization, error handling, preprocessing, and abstraction.