[
https://issues.apache.org/jira/browse/TINKERPOP3-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968960#comment-14968960
]
ASF GitHub Bot commented on TINKERPOP3-908:
-------------------------------------------
Github user spmallette commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/118#issuecomment-150181052
Aha - this is failing without the line breaks! Switched back to master and
still get:
```text
* source:
/home/smallette/git/apache/incubator-tinkerpop/docs/src/the-traversal.asciidoc
target:
/home/smallette/git/apache/incubator-tinkerpop/target/postprocess-asciidoc/the-traversal.asciidoc
progress:
[================================================================>
] 64%No such property: keys for class: e
Display stack trace? [yN]
g.V().hasLabel('song').out('followedBy').groupCount().by('name').
groovysh_parse: 3: expecting EOF, found ')' @ line 3, column 11.
f.exists()) f.deleteDir()
```
Anyone know what this is? please fix in this branch if you know the
problem that way we can merge back to master cleanly.
> Use line breaks in documentation
> --------------------------------
>
> Key: TINKERPOP3-908
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-908
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
>
> It wasn't realized early on that asciidoc would respect line breaks (as being
> a single paragraph) in documentation so we tended to rely on intellij for
> artificial line breaks. The problem with that approach was that if a single
> letter changed in the docs within a paragraph it wasn't easy to see in a git
> diff what the change was because the whole line would be seen as a diff.
> This also made merging docs more difficult.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
