How to Write Custom ESLint Rules for Your JavaScript Project

While researching for a better (I was using JSHint before) and customizable JavaScript Code linting tool, I found ESLint and ever since have never looked back. ESList is modern, fast, customizable and cross-platform Node.js based static code analyser that looks for bad and problematic patterns in your JavaScript code.

Things that I love about ESLint tool:

  • Blazing fast scanning provides immediate feedback
  • Ability to add custom rules this is a huge win if you use a framework that is custom or is heavily customized.
  • Node.js based and thus easier to install on other developer's workstation.
  • How easy is to customize the rules and include other standard patterns in your project through its plugin feature (like SonarLint, etc.)

When do you need to write a custom rule

Your project requires some custom rules that is very specific to your project annd is not covered by ESLint's standard set of rules (259 rules currently).

Getting started with a custom rule

Writing your own rule involves the following steps:

 * Enforce using view.up() or view.down() methods instead of the expensive Ext.ComponentQuery.query() method 
"no-hms-ext-componentquery": {
    create: function(context) {
        return {
            CallExpression(node) {
                if (node.callee && node.callee.object && 
                        node.callee.object.object &&
                        node.callee.object.object.type === "Identifier" && 
               === "Ext" &&
               === "Identifier" &&
               === "ComponentQuery" &&
               === "Identifier" &&
               === "query") {
          , 'Avoid using Ext.ComponentQuery.query method, use view.down or popup.down method instead.');

Recent Posts

← Go Back