tsconfig - Ignore errors by ids
I know that all errors in TypeScript are optional, it'd be nice if we could declare which error ids we want to ignore. I.E. In the `tsconfig.json`: ```json { "compilerOptions":{ "ignoreErrors":[2403,2686,...] } } ``` The reason I say this is because a lot of these errors are just irratating... Like the error: ``` 'L' refers to a UMD global, but the current file is a module. Consider adding an import instead. ``` This isn't an actual type error. It's a code style suggestion, and is entirely subjective unlike invalid type errors. I find many little 'errors' like this and they are deeply frustrating, as they just fill the error log with rubbish... Allow us to define which error ids we want to ignore, and this won't happen.
Posted by sancarn on Feb 18, 2019, 2:12 AM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
tsconfig - Ignore errors by ids
I know that all errors in TypeScript are optional, it'd be nice if we could declare which error ids we want to ignore. I.E. In the `tsconfig.json`: ```json { "compilerOptions":{ "ignoreErrors":[2403,2686,...] } } ``` The reason I say this is because a lot of these errors are just irratating... Like the error: ``` 'L' refers to a UMD global, but the current file is a module. Consider adding an import instead. ``` This isn't an actual type error. It's a code style suggestion, and is entirely subjective unlike invalid type errors. I find many little 'errors' like this and they are deeply frustrating, as they just fill the error log with rubbish... Allow us to define which error ids we want to ignore, and this won't happen.
Comments (0)
No comments yet. Start the discussion.