-
Notifications
You must be signed in to change notification settings - Fork 81
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
"No JSDoc documentation was found for object ClassName#methodName" #147
Comments
…harness. See mozilla#147. The underlying bug where the TS analyzer cares what the cwd is remains.
Having seen that this issue was ref'd in a commit that was part of the release for Sphinx 3 compat, I just upgraded to sphinx-js 3.0 and tried again. However, now I'm seeing a different bug, which also prevents building the docs. Maybe someone knows where this could come from:
|
Can you pass |
Somehow missed your reply a week ago. I tried again with
|
If it helps: you can also try this yourself with our current branch. git clone [email protected]:remotestorage/remotestorage.js.git && \
cd remotestorage.js && \
npm install && \
npm run build:docs |
Thanks! |
Just a heads-up: we merged that pull request, so you can test this in our master branch now. I have adjusted the above bash script accordingly. |
Great; I appreciate it. I'm currently rewriting the TS support in its entirety, so we'll see if this persists after that. |
Finally had some time to test-run 3.1 against our code, and this issue has been solved now. Thanks a lot for all your work! |
Oh good! |
Sorry, I was thinking of the wrong issue! |
We're in the process of porting a library with existing sphinx-js docs to TypeScript, and I ran into this issue when it came to the docs. When trying to build the docs with TypeDoc, I get the following error (class and method names being actual ones, of course):
I don't know how Sphinx works in detail, but there seems to be some kind of global cache somewhere, because when I switch back to the master branch, it fails with the same error message with actual JSDoc (not TypeDoc), too. And even when I delete the entire folder and run it on a fresh clone, the error still persists.
I tried debugging it, but I couldn't find out how to be honest. Anyone has pointers that could help us find out what's going on?
The text was updated successfully, but these errors were encountered: