That's a good question. Our code as documentation mechanism is cumbersome
and seems to encourage poor documentation, but does check code snippets.
Focusing on documentation instead of code produces better documentation,
while risking errors. It's a trade off.


On Friday, May 10, 2013, Andres Taylor wrote:

> In community/server/src/main/resources/webadmin-html/deck/develop.html:
>
> > @@ -72,7 +74,7 @@
> >          For instance, to find Emil's friends:
> >      </p>
> >      <pre>START ee=node(*) MATCH (ee)-[:KNOWS]->(friends)
> > -WHERE n.name! = &quot;Emil&quot; RETURN friends;</pre>
> > +WHERE ee.name! = &quot;Emil&quot; RETURN friends;</pre>
>
> Would it be cost prohibitive to we can did this the same way we do other
> documentation and run the queries with assertions to catch errors like
> this? @nawroth <https://github.com/nawroth> @akollegger<https://github.com/akollegger>
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/neo4j/neo4j/pull/765/files#r4167522>
> .
>