'Avoid reporting warnings/errors for rule change until file is edited for another reason?
I've just made a load of updates to a project and changed the TypeScript, ESLint rules etc. One thing I did was introduce the no semi-colon rule.
Now there are warnings/errors about every single semi colon still in the project (obviously this is what I wanted). There are also errors related to the TypeScript config changes I made. But I don't want to fix them all in 1 PR as that will be massive.
Is it possible to ignore these issues unless you open / edit the file somehow or what is the best way to achieve this?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|
