-
Notifications
You must be signed in to change notification settings - Fork 22
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
Bulletproof ESLint config #61
Comments
motin
added a commit
to motin/shield-studies-addon-template
that referenced
this issue
Mar 22, 2018
motin
added a commit
to motin/shield-studies-addon-utils
that referenced
this issue
Mar 24, 2018
motin
added a commit
to motin/shield-studies-addon-utils
that referenced
this issue
Apr 3, 2018
gregglind
pushed a commit
that referenced
this issue
Apr 25, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reviewing PR #55 and noticed that I'm not seeing some ESLint errors/warnings locally, despite me injecting some sketchy JS. I think our config is slightly off. Maybe due to nested configs or something else.
Once PR55 lands, I'll take a peek and see if I can figure it out. This seems to give me closer to what I expected (after deleting nested /src/.eslintrc.json config):
The "valid-jsdoc" rule adds about 40 warnings, so we can probably turn that off for now, unless I can come up with a special config that ignores "Missing JSDoc @returns for function" warnings. Conversely, we could switch to eslint-plugin-jsdoc plugin which exposes more options. But in reality, all I care about now is invalid JSDocs or missing/inaccurate parameters.
The text was updated successfully, but these errors were encountered: