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

Resolve no-unused-vars, no-undef eslint warnings #14870

Closed
wants to merge 10 commits into from

Conversation

andyhot
Copy link

@andyhot andyhot commented Jan 24, 2017

No description provided.

@rwjblue
Copy link
Member

rwjblue commented Jan 25, 2017

Does this resolve all of the warnings for no-unused-vars / no-undef? If it does, we should consider having those rules trigger errors so that we do not regress in future iterations...

@andyhot
Copy link
Author

andyhot commented Jan 28, 2017

I'll push an update to this PR that handles all of them (including the tests).

I'm setting no-unused-vars to ["error", { "args": "none" }] so that it doesn't report unused arguments but I plan to explore this in an upcoming commit (or PR)

@andyhot andyhot force-pushed the topic-eslint branch 2 times, most recently from 44fe179 to aef5325 Compare January 29, 2017 00:27
@andyhot
Copy link
Author

andyhot commented Jan 29, 2017

I'd need some guidance on how to continue.

@homu
Copy link
Contributor

homu commented Mar 7, 2017

☔ The latest upstream changes (presumably #14985) made this pull request unmergeable. Please resolve the merge conflicts.

@homu
Copy link
Contributor

homu commented Mar 14, 2017

☔ The latest upstream changes (presumably #15014) made this pull request unmergeable. Please resolve the merge conflicts.

@andyhot
Copy link
Author

andyhot commented Feb 15, 2018

This has long become obsolete

@andyhot andyhot closed this Feb 15, 2018
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

Successfully merging this pull request may close these issues.

4 participants