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

Parsing fails with no indication of which file is broken #191

Open
dimageller opened this issue Oct 25, 2019 · 2 comments
Open

Parsing fails with no indication of which file is broken #191

dimageller opened this issue Oct 25, 2019 · 2 comments

Comments

@dimageller
Copy link

dimageller commented Oct 25, 2019

I had a function with JSDoc, where I forgot to specify type of object for input parameter, like below
/** Some function @param {} timeout */

While generating a document, parser failed, but it didn't indicate where

node_modules/jsdoctypeparser/lib/index.js:48 throw new Lexer.SyntaxError(e.message, typeExp, e.offset); ^ TypeLexerSyntaxError: Expected "!", "(", "*", "...", "=", "?", "function", "module", "{" or [a-zA-Z_$] but " " found.:

@ShivamJoker
Copy link

@tj I am also facing same. Is this package still maintained?

@Twipped
Copy link
Collaborator

Twipped commented Aug 4, 2022

@ShivamJoker TJ has not been the active maintainer for a long long time. The 0.x version is not extensively being maintained, largely because I haven't had the motivation to update it for the changes in jsdoctypeparser, and no one else has submitted a PR.

I am working on a complete rewrite of the project in my spare time, which will eventually become 1.0, but I don't know how long that will take.

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

No branches or pull requests

3 participants