Skip to content
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

Parser not works anymore if useReadMe is disabled #34

Closed
MCMicS opened this issue Jun 25, 2020 · 1 comment
Closed

Parser not works anymore if useReadMe is disabled #34

MCMicS opened this issue Jun 25, 2020 · 1 comment
Labels

Comments

@MCMicS
Copy link
Contributor

MCMicS commented Jun 25, 2020

Parser not works because it use wrong basedir for api lookup

  const apiDocsPath = options.baseDirectory || path.resolve('./', 'docs', 'api');
  const structuresPath = path.resolve(apiDocsPath, 'structures');

Leads to wrong api base Path.

{ [Error: ENOENT: no such file or directory, scandir 'electron-master/structures']
  errno: -4058,
  code: 'ENOENT',
  syscall: 'scandir',
  path:
   'electron-master/structures' }

commit: d8bec24

const apiDocsPath = options.baseDirectory || path.resolve('./', 'docs', 'api');

@MCMicS MCMicS changed the title Parser not works anymore i useReadMe is disabled Parser not works anymore if useReadMe is disabled Jun 25, 2020
MCMicS added a commit to MCMicS/docs-parser that referenced this issue Jun 25, 2020
@electron-bot
Copy link

🎉 This issue has been resolved in version 0.9.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants