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

Allow linter warnings but be strict on rules #187

Merged
merged 5 commits into from
Aug 7, 2020

Conversation

Half-Shot
Copy link
Contributor

So we can have greater visibility on what needs fixing, rather than resorting to ignore comments.

@Half-Shot Half-Shot requested a review from a team August 6, 2020 17:03
Copy link
Contributor

@jaller94 jaller94 left a comment

Choose a reason for hiding this comment

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

Yay for making warnings not fail CI.

"@typescript-eslint/ban-ts-ignore": 0,
"no-unused-vars": 0,
"@typescript-eslint/ban-ts-ignore": "off",
"no-unused-vars": "off",
Copy link
Contributor

Choose a reason for hiding this comment

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

🤨

Copy link
Contributor Author

Choose a reason for hiding this comment

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

?

Copy link
Contributor

Choose a reason for hiding this comment

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

I am wondering why unused variables need to be allowed for now, but I don't think it's a blocker.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, it was before. I just changed it to a more readable string.

@Half-Shot Half-Shot merged commit 691718f into develop Aug 7, 2020
@jaller94 jaller94 deleted the hs/allow-warnings-but-be-more-strict branch August 7, 2020 10:47
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.

2 participants