Pedro Augusto de Paula Barbosa

> I believe all negative `Array.every()` can write in positive `Array.some()` They can, but I think it might worsen readability sometimes.

> Opinionated, difficult/impossible to implement, and likely super annoying in practice. I agree with this. Any ideas on how to make this rule not have lots of annoying false positives?

@sindresorhus I believe this issue shouldn't have been closed. PR #505 contained the sentence `doesn't fix #466` but GitHub looked at `fix #466` and went out to close this. https://github.com/isaacs/github/issues/1871

I think that's a good idea. I suggest having a new option `--always-show-warnings` (or something like that) that is false by default. When it's false (the default), I'd like to...

@jimmywarting His point is that `Number.parseInt(x, 10)` should be replaced by `Math.floor(Number(x))` or similar - not to omit the radix.

I've had this happen to me several times already as well. I just go back and click the move again; sometimes I need to play some fake moves to see...

I'd recommend `denylist` instead of `blocklist`, I've seen `denylist` used in many places around but haven't seen `blocklist` yet. Just to make it closer to the trend.

I believe the correct usage is `loading={}` instead of `loading={YourComponent}`

Is it acceptable to expect [`as const`](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-4.html#const-assertions) being used when setting `this.inputs`? ```ts this.inputs = { /* ... things here that I will think of and suggest soon ... */...

Pong! Sorry for the delay, I have been quite busy, but hopefully next week I will be able to help you. Sorry!!