-
Notifications
You must be signed in to change notification settings - Fork 203
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
Unidentifiable Errors #11
Comments
@benderTheCrime Hi! Thank you for reporting this issue! I want to fix the problems.
Could you tell me about the source codes or repository that reproduces the problems? |
https://github.com/benderTheCrime/angie in the |
@benderTheCrime I will try to fix the problem. |
This simple code crashes a standard run:
I hope it will help you somehow. |
@Crazy-Ivan can you try doing a run with by aliasing the function and seeing if that helps? export default function test() {
return 'Do something';
} I'm just trying to get a sense as to whether this issue is related generally to namespacing? I've noticed some weirdness in what is actually displayed once I've generated the docs as well. It does not show all of the exposed classes or functions. |
Yes, works like a charm if funcion/class etc has a name. The problem is with anonymous functions/classes. I think it is related to this issue #13 |
@Crazy-Ivan Hi You can temporarily work around this issue by using /**
* @name thisFunctionName
*/
export default function(){
} |
@benderTheCrime I fixed this issue and I will release the fixing in next version! |
Thanks for putting together a library that generates ES6 docs! I ran into a few errors with a standard run:
esdoc.json:
errors:
In the first case, I simply commented out the offending line:
//if (node2.id.name !== node1.declaration.name) continue;
In the second, I wrapped the block in an if statement, which checked for the argument passed to the function:
In this way, I got the commands to work, but I'm not sure it generated proper docs.
Let me know if there is anything else I can do to help you reproduce. I would also like to see a config option to turn off stdout if there is not one already.
The text was updated successfully, but these errors were encountered: