-
Notifications
You must be signed in to change notification settings - Fork 13
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
grunt-dox task fails with ENOENT error sourcing from _head.jade, line 8 #15
Comments
Hey @somecallmechief, I'm looking into this. I believe this is definitely an issue with dox-foundation and not grunt-dox. I'll close this out when I figure something out |
Could you give me an example of the dox-foundation command that you ran? I'm having trouble reproducing the error |
Alrighty, I pulled down your repo and play around for a while. I made some changes that appear to have worked. I'm pushing dox-foundation I'm not sure dox-foundation will be the right tool though! There are some serious contraints on the template that seem to fail when you get to a project as large as yours. I'm happy to take suggestions and even more so to accept pull requests! |
@mattmcmanus Thanks for looking into it! I'll give it another whirl tomorrow and see how far I get. [Update] That indeed fixes the error I reported, and I do now understand your comment. Given the current template, you do start to see the constraints when using a project like mine. Still, thanks for your help. |
Just as with issue #14, I've been trying to autogenerate API documentation for my project, OJ. I'm stuck behind bugs in grunt-jsdoc and grunt-jsduck, and I found dox and thus grunt-dox by proxy.
I used the same configuration as in the readme, but I get an exception every time, full text here: https://gist.github.com/somecallmechief/31c272bc0d6ae554202a.
I get a similar error when trying to use dox-foundation; but when I call dox directly I get a JSON file that looks correct.
The text was updated successfully, but these errors were encountered: