{"id":1710,"date":"2023-11-02T05:00:00","date_gmt":"2023-11-02T12:00:00","guid":{"rendered":"https:\/\/www.angulartraining.com\/daily-newsletter\/?p=1710"},"modified":"2023-11-01T15:06:46","modified_gmt":"2023-11-01T22:06:46","slug":"rxjs-eslint-plugin-for-angular","status":"publish","type":"post","link":"https:\/\/www.angulartraining.com\/daily-newsletter\/rxjs-eslint-plugin-for-angular\/","title":{"rendered":"RxJs eslint plugin for Angular"},"content":{"rendered":"\n

Last month, I discussed eslint<\/a> and how to use that tool to parse your code and receive feedback on best practices and possible improvements.<\/p>\n\n\n\n

Today, I want to mention an eslint plugin explicitly written for RxJs with Angular: eslint-plugin-rxjs-angular.<\/a><\/p>\n\n\n\n

<\/p>\n\n\n\n

This plugin adds three possible validation rules:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

All rules are optional, and it doesn’t make sense to use all of them at once because these best practices are contradictory in the sense that the goal is for you to choose one of these three approaches and be 100% consistent with it:<\/p>\n\n\n\n

    \n
  1. The first rule<\/a> will enforce that you always use the async<\/code> pipe in your components.<\/li>\n\n\n\n
  2. The second rule<\/a> doesn’t care about the async<\/code> pipe but wants to ensure you unsubscribe on destroy.<\/li>\n\n\n\n
  3. The third rule<\/a> is the most specific, as it enforces that you always use a Subject with takeUntil<\/a><\/code> to unsubscribe in your components.<\/li>\n<\/ol>\n\n\n\n

    I’d suggest using the first rule only because we covered before that the async<\/code> pipe is the safest and most performant option<\/a>. And remember that you can always use the async<\/code> pipe<\/a>. There are no excuses!<\/p>\n","protected":false},"excerpt":{"rendered":"

    Last month, I discussed eslint and how to use that tool to parse your code and receive feedback on best practices and possible improvements. Today, I want to mention an eslint plugin explicitly written for RxJs with Angular: eslint-plugin-rxjs-angular. This plugin adds three possible validation rules: All rules are optional, and it doesn’t make sense […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,31,10,17],"tags":[],"class_list":["post-1710","post","type-post","status-publish","format-standard","hentry","category-angular","category-best-practices","category-rxjs","category-tools"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t