Skip to content

Commit fedcbd0

Browse files
committed
Include warning callout (fixes #7)
1 parent 1f987cd commit fedcbd0

File tree

1 file changed

+4
-2
lines changed
  • src/app/docs/woql-explanation

1 file changed

+4
-2
lines changed

src/app/docs/woql-explanation/page.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -69,14 +69,16 @@ triple(a, b, c).triple(d, e, f)
6969

7070
In the example above, fluent style 3 is more concise and unambiguous where WOQL functions that are chained together do not take sub-clauses (or commands.) As conjunction is frequently used, this concise form, where the `and()` is implicit, is more convenient in many situations.
7171

72-
!> Use implicit `and()` with care.
72+
{% callout type="warning" title="Use implicit `and()` with care" %}
7373

74-
?> if in doubt, use the explicit `and()` functional style as this clarifies which functions are sub-clauses of other functions.
74+
If in doubt, use the explicit `and()` functional style as this clarifies which functions are sub-clauses of other functions.
7575

7676
The conjunction is always applied to the function immediately to the left of the period `.` in the chain, and not to any functions further up the chain. If used improperly with clauses that take sub-clauses, it will produce improperly specified queries, especially with negation (`not`) and optional functions (`opt`).
7777

7878
For example, consider the following three queries. The first two are equivalent. However, the first query is incorrect and easy to misinterpret when the intended expression is that shown in the third query.
7979

80+
{% /callout %}
81+
8082
### Code: Fluent style implicit conjunction
8183

8284
```javascript

0 commit comments

Comments
 (0)