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: fix ESLint violation and lessen rule strictness #6081
Conversation
@@ -100,6 +100,11 @@ module.exports = { | |||
"@typescript-eslint/semi": 2, | |||
"@typescript-eslint/no-empty-function": 0, | |||
"@typescript-eslint/no-use-before-define": 0, | |||
// We have to use any on some types so the warning isn't valuable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah :( Long term we'll use the TS compiler strictness options to get rid of this but these warnings are adding no value.
@@ -67,7 +67,7 @@ describe('Emulation', () => { | |||
function dispatchTouch() { | |||
let fulfill; | |||
const promise = new Promise((x) => (fulfill = x)); | |||
window.ontouchstart = function (e) { | |||
window.ontouchstart = () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But why though?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the majority of the codebase + tests use arrow functions - this one stood out to me so I just swapped it out
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with curiosity question
e5085ea
to
10dc654
Compare
No description provided.