cheat sheet tags

Author: JPryce-Aklundh

modules/ROOT/pages/clauses/with.adoc

@@ -89,12 +89,15 @@ In the below example, the `WITH` clause binds all matched `Customer` nodes to a
 The bound nodes are `MAP` values which can then be referenced from the new variable.
 
 .Create a new variable bound to matched nodes
+// tag::clauses_with_new_variable[]
 [source, cypher]
 ----
 MATCH (c:Customer)-[:BUYS]->(:Product {name: 'Chocolate'})
 WITH c AS customer
 RETURN customer.firstName AS chocolateCustomer
 ----
+// end::clauses_with_new_variable[]
+
 
 .Result
 [role="queryresult",options="header,footer",cols="1*<m"]
@@ -137,6 +140,7 @@ Variable `p` not defined
 ----
 
 .Retain all variables with `WITH *`
+// tag::clauses_with_all_variables[]
 [source, cypher]
 ----
 MATCH (supplier:Supplier)-[r]->(product:Product)
@@ -145,6 +149,7 @@ RETURN supplier.name AS company,
        type(r) AS relType,
        product.name AS product
 ----
+// end::clauses_with_all_variables[]
 
 .Result
 [role="queryresult",options="header,footer",cols="3*<m"]
@@ -166,6 +171,7 @@ More specifically, a variable imported into a `CALL` subquery will be available
 In the below example, the `x` variable is imported to the inside scope of a `CALL` subquery, and is successfully referenced  by the `RETURN` clause even though the preceding `WITH` neglects to list it.
 
 .Variables cannot be de-scoped in the inner scope of a subquery
+// tag::clauses_with_subquery[]
 [source, cypher]
 ----
 WITH 11 AS x
@@ -176,6 +182,8 @@ CALL (x) {
 }
 RETURN x, a
 ----
+// end::clauses_with_subquery[]
+
 
 .Result
 [role="queryresult",options="header,footer",cols="2*<m"]
@@ -197,6 +205,7 @@ For more information, see xref:subqueries/call-subquery.adoc#import-variables[`C
 In the below query, the value of the `STRING` concatenation expression is bound to a new variable `customerFullName`, and the value from the expression `chocolate.price * (1 - customer.discount)` is bound to `chocolateNetPrice`, both of which are then available in the `RETURN` clause.
 
 .Bind values to variables
+// tag::clauses_with_bind_values[]
 [source, cypher]
 ----
 MATCH (customer:Customer)-[:BUYS]->(chocolate:Product {name: 'Chocolate'})
@@ -205,6 +214,8 @@ WITH customer.firstName || ' ' || customer.lastName AS customerFullName,
 RETURN customerFullName,
        chocolateNetPrice
 ----
+// end::clauses_with_bind_values[]
+
 
 .Result
 [role="queryresult",options="header,footer",cols="2*<m"]
@@ -221,6 +232,7 @@ RETURN customerFullName,
 Because `WITH` can be used to assign variables to the values of expressions, it can be used to chain expressions.
 
 .Chain expressions using `WITH`
+// tag::clauses_with_chain_expressions[]
 [source, cypher]
 ----
 MATCH (p:Product)
@@ -237,6 +249,7 @@ RETURN p.name AS product,
        discountCategory
 ORDER BY price
 ----
+// end::clauses_with_chain_expressions[]
 
 .Result
 [role="queryresult",options="header,footer", cols="4*<m"]
@@ -261,6 +274,7 @@ In this example, the xref:functions/aggregating.adoc#functions-sum[`sum()`] func
 The xref:functions/aggregating.adoc#functions-collect[`collect()`] function is used to collect each product into  `LIST` values bound to the `productsBought` variable.
 
 .`WITH` performing aggregations
+// tag::clauses_with_aggregations[]
 [source, cypher]
 ----
 MATCH (c:Customer)-[:BUYS]->(p:Product)
@@ -272,6 +286,8 @@ RETURN customer,
        productsBought
 ORDER BY totalSpent DESC
 ----
+// end::clauses_with_aggregations[]
+
 
 .Result
 [role="queryresult",options="header,footer", cols="3*<m"]
@@ -297,13 +313,15 @@ ORDER BY totalSpent DESC
 In the below query, `WITH DISTINCT` is used to remove any duplicate `discount` property values from `Customer` nodes.
 
 .`WITH DISTINCT` to remove duplicate values
+// tag::clauses_with_remove_duplicates[]
 [source, cypher]
 ----
 MATCH (c:Customer)
 WITH DISTINCT c.discount AS discountRates
 RETURN discountRates
 ORDER BY discountRates
 ----
+// end::clauses_with_remove_duplicates[]
 
 .Result
 [role="queryresult",options="header,footer", cols="1*<m"]
@@ -357,6 +375,7 @@ In the next example, `LIMIT` is used to only retain the top 3 customers with the
 Then, the xref:clauses/set.adoc[`SET`] assigns a new property (`topSpender = true`) to those customers who have spent the most.
 
 .Limit results with `LIMIT`
+// tag::clauses_with_ordering_pagination[]
 [source, cypher]
 ----
 MATCH (c:Customer)-[:BUYS]->(p:Product)
@@ -369,6 +388,8 @@ RETURN c.firstName AS customer,
        totalSpent,
        c.topSpender AS topSpender
 ----
+// end::clauses_with_ordering_pagination[]
+
 
 [role="queryresult",options="header,footer", cols="3*<m"]
 |===
@@ -470,6 +491,7 @@ In the below query, `WITH` and `WHERE` are used to filter out any `Supplier` nod
 Note the use of `DISTINCT` inside `collect()` to remove any duplicate `Customer` nodes.
 
 .Filter property values using `WITH` and `WHERE`
+// tag::clauses_with_filtering[]
 [source, cypher]
 ----
 MATCH (s:Supplier)-[:SUPPLIES]->(p:Product)<-[:BUYS]-(c:Customer)
@@ -481,6 +503,7 @@ RETURN s.name AS supplier,
        totalSales,
        uniqueCustomers
 ----
+// end::clauses_with_filtering[]
 
 [role="queryresult",options="header,footer", cols="3*<m"]
 |===
@@ -498,6 +521,7 @@ RETURN s.name AS supplier,
 If a write clause is followed by a read clause, `WITH` must be used as a separator between the two.
 
 .`WITH` used as a separator between a write clause and a read clause
+// tag::clauses_with_combine_write_read[]
 [source, cypher]
 ----
 MATCH (yusuf:Customer {firstName: 'Yusuf'}),
@@ -511,6 +535,7 @@ RETURN collect(p.name) AS yusufPurchases,
        r.date AS date
 ORDER BY date DESC
 ----
+// end::clauses_with_combine_write_read[]
 
 [role="queryresult",options="header,footer", cols="2*<m"]
 |===