codelyzer
codelyzer copied to clipboard
mgechev
Static analysis for Angular projects.
Is there a way to use the `"i18n": [false,"check-text"]` rule would pass for any text node containing only numbers or other non-word symbols even if the wrapper element is missing...
**Describe the bug** Column numbers are off by one when codelyzer reports errors in template files (works fine in inline templates). With an inline template, errors are reported at the...
**Describe the bug** Errors in the console link to absolute paths. We should use relative paths. **Context and configuration** Please share: a11y rules are what are specifically linking to absolute...
I just ran into a bug with a negated async pipe. Rule `templates-no-negated-async` didn't catch it because the parens were missing: ``` *ngIf="!loading$ | async" ``` This condition is perfectly...
with template markup as: ``` {{tData.sectionText}} foo bar ``` `xi18n` triggers the following: > Could not mark an element as translatable inside a translatable section `
In the [latest TSLint's release](https://github.com/palantir/tslint/blob/master/CHANGELOG.md#v5130), they marked `RuleWalker` as deprecated. Apparently, [RuleWalker-based rules are slow and should be avoided](https://github.com/palantir/tslint/issues/2522). Considering this, what should we do with the current rules? @mgechev...
**What I'm trying to do:** Write a custom rule that enforces event handler naming consistency, by copying and modifying the code from [banana-in-box](https://github.com/mgechev/codelyzer/blob/master/src/bananaInBoxRule.ts). **Problem:** The custom rule is not visiting...
**Config:** ```JSON { "rules": { "template-conditional-complexity": [ true, 2 ] } } ``` **1st. case:** (when the *ngIf contains a `pipe` it doesn't work well) ```ts @Component({ template: ` Content...
- codelyzer 4.1.0 - Angular 5.2.1 - TypeScript 2.6.2 ` "i18n": [true, "check-text"]` does not work for this examples: ``` Veröffentlichen ``` > edit-article.component.html[35, 110]: Each element containing text node...
