-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not all comments being parsed. #149
Comments
As @tomekwi found in #152, it's |
Changing the line from .option('-t, --template <destination>', 'The template to use. Defaults to readem\'s own template.') to .option('-t, --template <destination>', "The template to use. Defaults to readem's own template.") also results in the problem. |
Changing the line to .option('-t, --template <destination>', 'The template to use. Defaults to the template shipped with readem.') temporarily solves the problem. :) |
This is still an issue |
When Mixed Mode of Famo.us comes out (very soon) I'll be back to developing my UI components, and documenting them, and hence I'll be back to dox and will check this out. @ChiperSoft I see the context parsers array. Looks good. (: |
Version 0.8.1 has been published with @ammojamo's fix for this. |
Sweeeet. I'll be back to this soon. Dropped Famous, and am working on an engine from scratch at http://infamous.io (name subject to change), which I'll need to document eventually. :D |
parseComments
is returning an Array with a length of two for the following file even though it has more than two comments: https://github.com/trusktr/readem/blob/d51f9e899702318526bd7322e10bb1e8fbd671f9/bin/read'em.jsThe text was updated successfully, but these errors were encountered: