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.

Sign up for GitHub

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

Jump to bottom

Rule: Do not use 'new' for side effects #78

Closed
ilyavolodin opened this issue Jul 18, 2013 · 0 comments · Fixed by #79
Closed

Rule: Do not use 'new' for side effects #78

ilyavolodin opened this issue Jul 18, 2013 · 0 comments · Fixed by #79
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion

Comments

@ilyavolodin
Copy link
Member

See:
http://jslinterrors.com/do-not-use-new-for-side-effects/

The rule ID should be "no-new" and should be enabled as a warning by default.
@ilyavolodin ilyavolodin mentioned this issue Jul 18, 2013
Merged
@btmills btmills mentioned this issue Mar 9, 2014
Closed
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Feb 7, 2018
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Feb 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Rule: Do not use 'new' for side effects
1 participant
@ilyavolodin