@typescript-eslint/no-floating-promises conflicts no-void

[01397]

Summary

When there is no need to wait for a Promise to be resolved, two rules are in conflict.

• @typescript-eslint/no-floating-promises recommends to using void operator to as an explicit marker.
• no-void prohibits using void

Details

• The ignoreVoid option of @typescript-eslint/no-floating-promises is set to true by default.
  https://typescript-eslint.io/rules/no-floating-promises/#ignorevoid
• no-void is declared in best-practices.js

The ESLint official docs recommends using the allowAsStatement option of no-void when using two rules.

With this option set to true, and if you are using no-void, you should turn on the allowAsStatement option.
https://typescript-eslint.io/rules/no-floating-promises/#ignorevoid

Possible solutions

• Add allowAsStatement option to no-void to developer can use void as markers
• Add ignoreVoid: false to @typescript/no-floating-promises, and developer use eslint-disable-next-line as markers.