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

chore: check warnings and errors from gulp lint #11452

Closed
DanielRuf opened this issue Aug 14, 2018 · 7 comments
Closed

chore: check warnings and errors from gulp lint #11452

DanielRuf opened this issue Aug 14, 2018 · 7 comments

Comments

@DanielRuf
Copy link
Contributor

Description

Check warnings and errors from gulp lint.

@aorinevo
Copy link
Contributor

Hi @DanielRuf, is the scope of work for this issue to resolve all warnings and errors from gulp lint?

@ncoden
Copy link
Contributor

ncoden commented Aug 15, 2018

Hi @DanielRuf. I had some time so I investigated on why the Sass linting errors were not shown in the build task. See #11454

@pebutler3
Copy link
Contributor

@joeworkman is it cool if I start tackling these errors?

@joeworkman
Copy link
Member

@pebutler3 That would be amazing! I am hosting a conference this weekend. So I have had my head in the sand preparing for that.

@pebutler3
Copy link
Contributor

How does everyone feel about disabling this "no-extra-parens": 1, in .eslintrc ?

I bring this up because this rule is being called out in quite a few math related scenarios where I believe the code is more readable with the parens.

@joeworkman joeworkman reopened this Oct 26, 2021
@DanielRuf
Copy link
Contributor Author

How does everyone feel about disabling this "no-extra-parens": 1, in .eslintrc ?

I bring this up because this rule is being called out in quite a few math related scenarios where I believe the code is more readable with the parens.

We should create a new issue. The original issue was about the sasslint errors.

For eslintrc and other stuff, please open new issues.

@joeworkman
Copy link
Member

@pebutler3 I created a new issue.

#12299

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

Successfully merging a pull request may close this issue.

5 participants