A core concept of groc
is that your code is grouped into a project, and that there is a certain
amount of context that it lends to your documentation.
A project:
lib/some/source.file
maps
to doc/some/source.file
and not doc/lib/some/source.file
.Annoyingly, we seem to be hitting a race condition within Node 0.10's emulation for old-style streams. For now, we're dropping concurrent doc generation to play it safe. People are still using groc with 0.6.
This is both a performance (over-)optimization and debugging aid. Instead of spamming the system with file I/O and overhead all at once, we only process a certain number of source files concurrently. This is similar to what graceful-fs accomplishes.
Where the magic happens. Currently, the only supported option is:
styles.Default
We need to ensure that the project root is a strip prefix so that we properly generate relative paths for our files. Since strip prefixes are relative, it must be the first prefix, so that they can strip from the remainder.
groc API