eslint-plugin-angular

  • This repository will give access to new rules for the ESLint tool.
  • There are some useful references for creating new rules.
  • Specificly useful are:

    We can use a property, defined in the ESLint configuration file, in order to know which version is used : Angular 1 or Angular 2.

  • based on this property, you can create rules for each version.
  • And in your rule, you can access to this property thanks to the object :

    Here is the basic configuration for the rules defined in the ESLint plugin, in order to be compatible with the guideline provided by @johnpapa :

ESLint rules for AngularJS projects

@EmmanuelDemey: A new version of my @geteslint #angularjs plugin is out ! 2.3.0 👏🎖️

This repository will give access to new rules for the ESLint tool. You should use it only if you are developing an AngularJS application.

Since the 0.0.4 release, some rules defined in John Papa’s Guideline have been implemented. In the description below, you will have a link to the corresponding part of the guideline, in order to have more information.

Rules in eslint-plugin-angular are divided into several categories to help you better understand their value.

The following rules detect patterns that can lead to errors.

These are rules designed to prevent you from making mistakes. They either prescribe a better way of doing something or help you avoid footguns..

These rules prevent you from using deprecated angular features.

These rules help you to specify several naming conventions.

Angular often provide multi ways to to something. These rules help you to define convention for your project.

These rules help you to enforce the usage of angular wrappers.

These rules help you avoiding misspellings.

It is an opensource project. Any help will be very useful. You can :

branch.

. @Gillespie59 will then publish the new release to the npm registry.

We appreciate contributions and the following notes will help you before you open a Pull Request.

Have a look at the existing issues. There may exist similar issues with useful information.

There are some useful references for creating new rules. Specificly useful are:

We can use a property, defined in the ESLint configuration file, in order to know which version is used : Angular 1 or Angular 2. based on this property, you can create rules for each version.

object :

Here is the basic configuration for the rules defined in the ESLint plugin, in order to be compatible with the guideline provided by @johnpapa :

eslint-plugin-angular

You might also like More from author

Comments are closed, but trackbacks and pingbacks are open.