Skip to content

Commit 22bf630

Browse files
authored
Update query-language.md
1 parent a0110f2 commit 22bf630

File tree

1 file changed

+18
-18
lines changed

1 file changed

+18
-18
lines changed

src/api/public-api/query-language.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -87,12 +87,12 @@ The following tables list the query languages's available functions.
8787
| Notes | Only valid within a `where` function or a Reducer. |
8888
| Example | `context('page.url')` |
8989

90-
| `literal` | |
91-
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
92-
| Syntax | `literal({a: Any})` <br> `a` - the value to treat as a literal expression |
90+
| `literal` | |
91+
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
92+
| Syntax | `literal({a: Any})` <br> `a` - the value to treat as a literal expression |
9393
| 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)` |
9696

9797

9898

@@ -287,19 +287,19 @@ The following tables list the query languages's available functions.
287287
| Description | Matches when the value does not exactly match one of the values from the parameter array. |
288288
| Example | `none_of('shoes','shirts')` |
289289

290-
| `before_date` | |
291-
| ------------- | --------------------------------------------------------- |
292-
| Syntax | `before_date({t: Timestamp})`<br>`t` - ISO 8601 timestamp |
293-
| Return Type | `Comparator` |
294-
| Notes | `string` format can also be use |
295-
| Example | `before_date('2023-12-07T18:50:00Z')` |
296-
297-
| `after_date` | |
298-
| ------------ | -------------------------------------------------------- |
299-
| Syntax | `after_date({t: Timestamp})`<br>`t` - ISO 8601 timestamp |
300-
| Return Type | `Comparator` |
301-
| Notes | `string` format can also be use |
302-
| Example | `after_date('2023-12-07T18:50:00Z')` |
290+
| `before_date` | |
291+
| ------------- | ---------------------------------------------------------------------------- |
292+
| Syntax | `before_date({t: Timestamp})`<br>`t` - ISO 8601 timestamp |
293+
| Return Type | `Comparator` |
294+
| Notes | `string` format can also be use |
295+
| Example | `before_date(2023-12-07T18:50:00Z)` or `before_date('2023-12-07T18:50:00Z')` |
296+
297+
| `after_date` | |
298+
| ------------ | -------------------------------------------------------------------------- |
299+
| Syntax | `after_date({t: Timestamp})`<br>`t` - ISO 8601 timestamp |
300+
| Return Type | `Comparator` |
301+
| Notes | `string` format can also be use |
302+
| Example | `after_date(2023-12-07T18:50:00Z)` or `after_date('2023-12-07T18:50:00Z')` |
303303

304304
| `within_last` | |
305305
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

0 commit comments

Comments
 (0)