Decide on what case to document Cypher functions in #151

Closed
lassewesth opened this Issue Nov 12, 2012 · 4 comments

Projects

None yet

2 participants

@lassewesth
Member

@peterneubauer: 'see http://docs.neo4j.org/chunked/snapshot/query-function.html#_scalar_functions for an example on how LENGTH() is documented both uppercase and lowercase.

We might want to enforce one variant.'

@lassewesth
Member

valueCount: 1
values:

@lassewesth
Member

@nawroth: Generally speaking it's easier to read lowercase than uppercase -- from this point of view, I'd prefer all keywords to be lowercase (also those currently forced to uppercase). The syntax highlighting makes sure they stand out visually anyhow.

The reasons I can see to use uppercase is that the PDF version doesn't have syntax highlighting and to look like SQL in this respect (at least traditionally uppercase keywords I think). Maybe go for lowercase on all keywords and fix syntax HL in the PDF output in a not too distant future?

@lassewesth
Member

@systay: Just pick one. I don't mind either way.

On Tue, Mar 6, 2012 at 5:01 PM, Peter Neubauer <
reply@reply.github.com

wrote:

see
http://docs.neo4j.org/chunked/snapshot/query-function.html#_scalar_functionsfor an example on how LENGTH() is documented both uppercase and lowercase.

We might want to enforce one variant.


Reply to this email directly or view it on GitHub:
https://github.com/neo4j/community/issues/313

@lassewesth
Member

@nawroth: I'd say we should go for the more modern look of lowercase then.

@nawroth nawroth closed this Aug 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment