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
@@ -100,19 +100,19 @@ The first list variable is for [the event-values](#option-event-values), while t
100
100
101
101
### Extra data
102
102
103
-
If the event-values aren't enough for your desire, you can make use of the extra data feature. In the event itself, you can get the extra data with the not-yet-created data expression:
103
+
If the event-values aren't enough for your desire, you can make use of the extra data feature.
104
104
The syntax for adding event-values to a custom event is explained in [the event-values option](#option-event-values), and how to call an event with them is explained in [calling the event](#calling-the-event)
105
+
In the event itself, you can get the extra data with the data expression:
105
106
106
107
{% code-tabs %}
107
108
{% code-tabs-item title="Syntax" %}
108
109
```text
109
-
[extra] [event[-]] data %string%
110
+
[extra] [event[-]] data %strings%
110
111
```
111
112
{% endcode-tabs-item %}
112
113
{% endcode-tabs %}
113
-
In the syntax above, `%string%` is the index.
114
+
In the syntax above, `%strings%` is the index. This doesn't have to be plural, but can be.
114
115
115
-
{% hint style="danger" %}
116
-
This expression doesn't exist yet, until it is created, you can access it like so: `event.getData(%string%)`, where `%string%` is your index.
117
-
Why did I already document it if it doesn't exist yet? Because there's a decent chance I'll to do so forgot when I create the expression.
116
+
{% hint style="info" %}
117
+
It may look fancier to create a custom expression instead of using extra data. To do so, you need to call `event.getData(%index%)` to get the data value.
0 commit comments