Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
this codelyzer check seems broken for pipes
See original GitHub issuewhen using this command
“use-pipe-transform-interface”: false, // what is this – seems to be broken
it always fails and the code seems correct
@Pipe({name: 'orderByActive'})
export class OrderByActivePipe implements PipeTransform {
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Async pipes should not be negated - Stack Overflow
Angular's async pipes emit null initially, prior to the observable emitting any values, or the promise resolving. This can cause negations, like ...
Read more >codelyzer - npm
codelyzer. A set of tslint rules for static code analysis of Angular TypeScript projects. (If you are using ESLint check out the new ......
Read more >Angular Style Guide/Best Practices
Use codelyzer to follow this guide. Consider adjusting the rules in codelyzer to suit your needs. 12.2 Use TSLint. This is a static...
Read more >NG0302: Pipe not found! - Angular
it must be imported in an NgModule or a standalone component where it is used. the name used in a template must match...
Read more >My Top Favorite Tools for Angular Developers - Bits and Pieces
Augury helps us to detect anomalies, test out stuff (like where change ... or pipes or services or modules were all solved by...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
npm will install typescript 2.1.x
codelyzer/src/util/syntaxKind.ts > SyntaxKind.current().ImplementsKeyword returns 106 where it should be 107 starting from TypeScript version 2.1.0
The breaking change is here:
https://github.com/Microsoft/TypeScript/commit/6814c1d883791a1ad976f3146315de30e00dc0b9#diff-9a9b25e2950a3c3c611c9e2e095e2e41
before: ImplementsKeyword = 106 after: ImplementsKeyword = 107
The latest version is
beta.4: