-
Notifications
You must be signed in to change notification settings - Fork 486
Skip certain files #340
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
Comments
+1 for having the option to instruct Documentation to gracefully skip past what it perceives as syntax errors |
The |
Checked v4.0.0-beta — works fine 👍, thank you! |
💟 |
tmcw
added a commit
that referenced
this issue
Mar 19, 2016
👍 test-covered in fe2c5af |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey, thanks for the amazing work, I’m using Documentation and loving it.
Recently I’ve encountered a problem where Documentation throws an error when trying to parse a
.ejs
file which Iimport
. It works for me, because I have Browserify set up to automagically pre-compile.ejs
files and return a function with ejsify. But Documentation doesn’t know about that. I narrowed in down to Babylon — it seems like that’s what’s choking on non-js files. Is there a way to skip certain extensions or files?Similar error was thrown when I used this syntax in
.js
:This is a new rest syntax from ES6 and it totally works, but Documentation dies on it. Should it maybe just skip something it can’t parse instead of throwing?
The text was updated successfully, but these errors were encountered: