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

Add more eslint rules #4278

Merged
merged 1 commit into from
Sep 13, 2021
Merged

Add more eslint rules #4278

merged 1 commit into from
Sep 13, 2021

Conversation

Swiftb0y
Copy link
Member

I frequently find myself manually correcting many of these during code review so I figured I'd add them to the eslint rules to be enforced automatically. I'm open to removing some rules if others disagree with my style-choices. I also did not think much about severity yet, so I just categorized everything as "warn" for now, but thats also up for discussion.
I also removed the deprecated print() global while I was at it.

Copy link
Contributor

@uklotzde uklotzde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Opinions anyone?

@Holzhaus
Copy link
Member

LGTM, but i think this PR should be split up. Some new rules should already go into 2.3.

@Swiftb0y
Copy link
Member Author

Which rules in particular or just all of them?

@Holzhaus
Copy link
Member

Let and const don't work in 2.3. And I think bind does neither. So all rules that relate to that (e. g. no-var, prefer-const,...).

@Swiftb0y
Copy link
Member Author

merge? This way I can merge 2.3 into main and issue the follow-up PR to main.

@Holzhaus Holzhaus merged commit 3cbcb92 into mixxxdj:2.3 Sep 13, 2021
@Swiftb0y Swiftb0y deleted the eslint-rules branch September 13, 2021 12:10
@Swiftb0y Swiftb0y restored the eslint-rules branch September 13, 2021 12:19
@Swiftb0y Swiftb0y mentioned this pull request Sep 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants