foreach doesn't properly format the query string about decypher

[Yomguithereal]

That's an interesting issue @dmk255. I should look into it and adapt the API to this issue I think.

[dan-kez]

Thanks for the quick response! It'd be great if the API could support this.

[Yomguithereal]

What I propose to you is to add an argument to the forEach method taking the inner statement of the loop. Something along this:

cypher.foreach('name in {names}', 'MERGE (c {name: name})', {names: ['a']});

What do you think?

[dan-kez]

That definitely could work. I think having the option to put another query
object in would also be great.

E.g
subquery.merge('MERGE (c {name: name})');

cypher.foreach('name in {names}', subquery, {names: ['a']});

This would also combine the parameter objects from the subquery and the
parent query.

What do you think?

[Yomguithereal]

The only thing I need to know here, and excuse my rusty cypher, is whether the inner statement you can pass to the FOREACH can be more complex than a single statement?

[dan-kez]

Yes it can. There are some limitations on what you can do in the inner
query. For example you can't use the CALL. I'm not sure of all the
limitations though.

[Yomguithereal]

Ok. Do you have other statements in mind that behave like the FOREACH one? So I can handle them too.

[dan-kez]

Ther are a few that are similar but not the same. Take a look at this
document:

http://neo4j.com/docs/pdf/neo4j-cypher-refcard-stable.pdf

[Yomguithereal]

Just published v0.9.0 on npm @dmk255. Tell me whether this fits your needs and don't hesitate to come back if you find some more things needing to get tweaked.