Monorepo for all the tooling related to using ESLint with Angular
MIT License
Bot releases are hidden (Show)
allowStatic
option (#482) (89926d8)checkAttributes
properly (#467) (20e54d7)data
and suggestions
individually for each error (#491) (70b01bd)ng add
include a lint command if none exists (#481) (ae49af4)Conditional
and its keys to VisitorKeys
(#445) (5ad0f1a)update to angular v12 (c80008d)
eslint-plugin-template: no-negated-async no longer performs equality checks (#399)
@angular-eslint/template/eqeqeq
rule to your config if you want to continue with the same functionality around equality checks. This will be applied for you by ng update
automatically.We have provided automated migrations for you to move to v4.
All you need to do is run the update schematics for @angular-eslint
:
npx ng update @angular-eslint/schematics
NOTE: For this release, there are no automated migrations to be run, other than automatically updating the version number of your other @angular-eslint
packages.
Passing --collection=@angular-eslint/schematics
to ng new
is no longer supported:
@angular-eslint
to a workspace - run ng add @angular-eslint/schematics
- regardless of whether that workspace is brand new or has existed for a while.We have introduced two new options to the convert-tslint-to-eslint
schematic:
--remove-tslint-if-no-more-tslint-targets
so that we remove TSLint and Codelyzer from the workspace automatically if we detect you have no TSLint usage remaining (true
by default).--ignore-existing-tslint-config
so that we can jump straight to the up to date recommended ESLint setup, without converting the previous Angular CLI TSLint setup, which is unnecessary for brand new projects (false
by default).PR #388 (f92b184)
We have provided automated migrations for you to move to v3.
All you need to do is run the update schematics for @angular-eslint
:
npx ng update @angular-eslint/schematics
recommended
configs from @angular-eslint/eslin-plugin
now only configures rules directly from that plugin. This provides an overall more intuitive experience when stacking the recommended config with other plugins from the ecosystem. If you wish to continue having the same experience (with mixed @angular-eslint
and @typescript-eslint
rules in the configs you inherit from you can add the new recommended--extra
config to your ESLint extends in the relevant config.E.g. extract from .eslintrc.json
"extends": [
"plugin:@angular-eslint/recommended",
+ "plugin:@angular-eslint/recommended--extra",
],
Within the builder
, linting now always runs relative to your workspace root. This should not have any impact on my workflows but is important if you run ng lint
from within subdirectories of your workspace.
Within the builder
, we always make a call to format, even if the lint results are empty. This is important for non-default formatters.
We have removed the hard peerDependency on the 3rd party eslint plugins import
jsdoc
and prefer-arrow
. These plugins are only required if you are converted an existing workspace to TSLint and they will still be installed on demand in that scenario.
Within the eslint-plugin
, the component-max-inline-declarations
rule will no longer accept negative values as input. Previously it would silently use the default values in this case. An automated migration is provided for this change as part of the ng update
schematics.
We have provided automated migrations for you to move to v2.
All you need to do is first update to Angular and Angular CLI v11.2.0 or above (see https://update.angular.io for full instructions relating to Angular updates):
npx ng update @angular/cli @angular/core
And then run the update schematics for @angular-eslint
:
npx ng update @angular-eslint/schematics
The format of results output has changed
The use-pipe-decorator
rule no longer exists for use
feat(template-parser): updated use of parseTemplate to improve loc data
feat(schematics): change way indent and quotes are handled by conversion schematics
Published by JamesHenry over 3 years ago
Published by JamesHenry almost 4 years ago
Published by JamesHenry almost 4 years ago
π
The thing the rounded us out to v1 is the ability to create new workspaces which contain no TSLint or Codelyzer at all.
Additionally, versus the pre-releases, the recommended config no longer contains any stylistic rules. It was an oversight that they were in there in the first place.
(If you wish to enable stylistic rules in your lint setup you can always do so in your own config)
Hereβs to a great 2021!