Codelyzer: [feat] add a warning when not using trackBy with ngFor

[mattlewis92]

Even though its considered best practise, I always forget to add a trackBy when using ngFor. It would be awesome to have a rule to enforce this in templates. Since invalid usage of trackBy is currently swallowed silently by angular, as a stretch it would be cool if the rule validates the trackBy expression as well. If you're in favour of this I would love to take a go at a PR for this feature. Thanks! 😄

[mgechev]

Sounds like a good suggestion. There's issue related to the errors reporting in ngFor. Once this is fixed it'll be relatively easy to implement.

[maxime1992]

I came here to post that but @mattlewis92 did it 2 days ago :smile: !
Indeed, I think it would be a really nice feature! :beers:

[mgechev]

Will move it to the next release in order to not bloat 3.2.0.

[markwhitfeld]

This would be an amazing feature!
... and it even looks like @maxime1992 offered some beer to get it fixed 😉

[wKoza]

I keep track of that ;)