-
Notifications
You must be signed in to change notification settings - Fork 486
Cannot read property 'parseExtension' of undefined #869
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
I ran into this as well with the markdown formatter. It seems the formatter's You should be able to use it like this:
Maintainers, do the docs needs to be updated for the formatters? Or is the intent that the options should be optional? |
I think we need to make optional the second parameter. |
I encounter the same issue in |
This still happen today using ^8.0.0 and copy paste node markdown example execute it and you get a:
Even using a empty object as second parameter Edit: Actually using v6.2.0, which is the latest release as github says, it works! I dunno why npm installed the v8.x when running |
Version 9.1.1 and this happens again during the standard HTML generation. Adding the second option: {shallow: false} fixes it |
Version 13.0.1, same when trying to generate markdown. {shallow: false} as a second option fixes it. |
First of all thx for this great library, I've been using it with no problems for the past few months however since upgrading to the latest version I'm running into an error.
I'm using documentation version
5.1.1
installed as an npm module. But when I try to runnode generate-docs.js
(see file content of generate-docs below)I'm getting the following error:
Cannot read property 'parseExtension' of undefined
The error happens in
documentation/lib/merge_config.js
atline 72
where theconfig
passed into themergeConfig
function is undefined.I've had the script working on an older version where instead of the returned promise documentation.build() was using callback functions. I've tried to search stackoverflow but documentation is not the easiest search term :) From the documentation I understood that the
config.yml
was optional. Any help on a possible solution would be greatly appreciated :)Edit: some additional info, it works for version
4.0.0-beta.18
with the following code:The text was updated successfully, but these errors were encountered: