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
| Syntax |`literal({a: Any})` <br> `a` - the value to treat as a literal expression |
93
93
| Operations allowed in call-chain | None allowed; typically used within another function, like a comparison (with syntactic sugar, this would appear on the right side of the comparison). The outer function or comparison dictates the operations allowed in the call-chain. |
94
-
| Notes | Literals can be `int`s, `float`s, `string`s, or `timestamp`s, where `timestamp`s follow ISO 8601 format. Note that in general `string` is interchangeable with all other formats, except when used in a `property` chained to an `entity`. In this case, we recommend using `timestamp` over `string` based on the datatype you're targeting. |
95
-
| Example |`literal(100)` or `literal('value')` or `literal(2022-10-17T00:00:00)`|
94
+
| Notes | Literals can be `int`s, `float`s, `string`s, `date`s or `timestamp`s, where `date`s use the format `yyyy-mm-dd` and `timestamp`s follow ISO 8601 format. Note that in general `string` is interchangeable with all other formats, except when used in a `property` chained to an `entity`. In this case, we recommend matching the data type of the entity property being targeted.|
95
+
| Example |`literal(100)` or `literal('value')` or `literal(2022-10-17T00:00:00)`|
96
96
97
97
98
98
@@ -287,19 +287,19 @@ The following tables list the query languages's available functions.
287
287
| Description | Matches when the value does not exactly match one of the values from the parameter array. |
0 commit comments