Skip to content

Commit 511c5af

Browse files
Update documentation/workspace-params.adoc
Co-authored-by: Jessica Wright <49636617+AlexicaWright@users.noreply.github.com>
1 parent 12cc3fc commit 511c5af

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

documentation/workspace-params.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Parameters can be created and managed either via the parameters sidebar or by in
1515

1616
The Parameters sidebar provides dedicated UI inputs for most of the neo4j https://neo4j.com/docs/cypher-manual/current/values-and-types/property-structural-constructed/#property-types[property types].
1717
There are a few exceptions such as the https://neo4j.com/docs/cypher-manual/current/values-and-types/spatial/#spatial-values-point-type[Point] type and the setting of https://neo4j.com/docs/cypher-manual/current/values-and-types/property-structural-constructed/#constructed-types[constructed types].
18-
To support the setting of these types via the UI, we also provide a special option of `evaluated` in the type dropdown.
18+
To support the setting of these types via the UI, there is also a special option of `evaluated` in the type dropdown.
1919
This allows you to express any parameter type as you would using the right-hand part of the command syntax inlinecode:++:param pointParam => Point({x:1, y:1})++[], in this example `Point({x:1, y:1})` as the value to be evaluated.
2020

2121
For types that are not supported by the UI, or indeed if you prefer working with commands, the `:param` command provides the ability to set and manage parameters.

0 commit comments

Comments
 (0)