-
Notifications
You must be signed in to change notification settings - Fork 80
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
Rule 'name' didn't match at '' #61
Comments
sphinx-js is getting surprised by something jsdoc is emitting. This shouldn't happen and is probably my fault. Can you share the code you're running it over? Failing that, can you muck with the code to give me more to go on? Change this, in jsdoc.py… try:
app._sphinxjs_doclets_by_path.add(
doclet_full_path(d, root_for_relative_paths),
d)
except PathTaken as conflict:
conflicts.append(conflict.segments) …to this… try:
app._sphinxjs_doclets_by_path.add(
doclet_full_path(d, root_for_relative_paths),
d)
except PathTaken as conflict:
conflicts.append(conflict.segments)
except:
print(d) …and it'll spit out the raw jsdoc output when you run it again. Then send me the result. Thanks! |
Thanks for the quick response. Here's the problematic output and the code that triggers it (note: .js file renamed so it can be attached): problem.txt Cheers, |
Thanks for the info! I'll have a look. |
The trouble is these lines… * @method add_resize_handle
* representing the widget. …which cause the method's longname to be literally |
I should mention that this is third-party code, so setting Cheers, |
I spent some time trying to make us properly tolerate and escape chars like CR and LF (and the namepath separators like Interestingly, the root of your particular problem wasn't the line break at all; my parser is happy to eat that. It's the trailing period. Since it expects a namepath and period is a separator, it rightly expects something to come after it. |
Filed under #66. |
After adding sphinx-js to my documentation build, I get the following:
Here's my software stack:
I've tried experimenting with older versions of JSDoc and sphinx-js, but the symptoms are unchanged.
Here's the full traceback from the Sphinx log:
Cheers,
Tim
The text was updated successfully, but these errors were encountered: