You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
Similarly to the current option that takes a regex to match modules that should be allowed to be imported with side effects, it'd be nice if there were an option that would let me do the same thing except for files in my project.
Specifically, I have a main.ts that imports a decent number of external modules for their side effects by design, and it'd be more convenient to configure "no-import-side-effect": [true, {"ignore-file": "main\\.ts"}] than "no-import-side-effect": [true, {"ignore-module": "(angular|angular-material|jquery|zone\\.js|etc.)"]. This would also solve the problem that I don't necessarily want any other files performing side-effect imports of, say, zone.js just because main.ts does it.
The text was updated successfully, but these errors were encountered:
I'm fairly opposed to adding file names or globs to rule config options. tslint.json should define how to lint, not what to lint. I suggest using comment flags for your use case. Related: #629 (comment)
Similarly to the current option that takes a regex to match modules that should be allowed to be imported with side effects, it'd be nice if there were an option that would let me do the same thing except for files in my project.
Specifically, I have a main.ts that imports a decent number of external modules for their side effects by design, and it'd be more convenient to configure
"no-import-side-effect": [true, {"ignore-file": "main\\.ts"}]
than"no-import-side-effect": [true, {"ignore-module": "(angular|angular-material|jquery|zone\\.js|etc.)"]
. This would also solve the problem that I don't necessarily want any other files performing side-effect imports of, say, zone.js just because main.ts does it.The text was updated successfully, but these errors were encountered: