facebook pixelCodiga Analysis TypeScript Rules, category code style
BACK TO LIST

TypeScript rules

The Codiga Static Analysis engine checks TypeScript code and supports many popular libraries. If you are using React, NextJS, Vue or Angular: the engine will flag any issue in your codebase. Automate your code reviews with Codiga and merge with confidence.

@angular-eslint/component-class-suffix

Code style
Error

Detect if component doesn't have a descriptive suffix depending on its use, such as Component, Directive, Module, Pipe, or Service

Learn more

@typescript-eslint/camelcase

Code style
Warning

Detect all values and method definitions that do not use camelCase, they should.

@typescript-eslint/class-name-casing

Code style
Warning

Detect all classes and interfaces that do not follow the PascalCased name convention

@typescript-eslint/explicit-module-boundary-types

Code style
Warning

Detect if not all function types for arguments and return values are specified in the function signature

@typescript-eslint/interface-name-prefix

Code style
Informational

Detect interfaces that are not prefixed with "I" to differenciate them from regular classes. (e.g ISomeInterface as oposed to SomeInterface)

@typescript-eslint/triple-slash-reference

Code style
Warning

Detect any triple slash reference definitions in the top of the file, they should be replaced by the import style (e.g replace "/// <reference path="foo" />" by "import * as foo from 'foo';")

import/no-namespace

Code style
Error

Enforce a convention of not using namespace (a.k.a. "wildcard" *) imports.

import/prefer-default-export

Code style
Warning

When there is only a single export from a module, prefer using default export over named export.

no-mixed-spaces-and-tabs

Code style
Error

Detects when there are mixed spaces and tabs in a module definition

no-var

Code style
Error

Disallows var definition

prefer-const

Code style
Error

Suggest using const instead of var or let

prefer-rest-params

Code style
Error

Suggest using the rest parameters instead of arguments

prefer-spread

Code style
Error

Suggest using spread syntax instead of .apply()

typescript/interface-name-prefix

Code style
Informational

Require that interface names be prefixed with "I".

vue/multi-word-component-names

Code style
Warning

Component nam should always be multi-word

vue/component-definition-name-casing

Code style
Warning

Enforce specific casing for component definition name