Files
argo-cd/docs/developer-guide/static-code-analysis.md
Mayursinh Sarvaiya 7945b26d95 chore(ui-dev): migrate tslint to eslint (#11652) (#18079)
* feat(ui): setup eslint

Signed-off-by: Mayursinh Sarvaiya <marvinduff97@gmail.com>

* chore(ui): update `lint:fix` command

Signed-off-by: Mayursinh Sarvaiya <marvinduff97@gmail.com>

* fix(ui-lint): run `yarn lint:fix`

> solve remaining manually

Signed-off-by: Mayursinh Sarvaiya <marvinduff97@gmail.com>

* chore(ui): remove tslint from `ui`

Signed-off-by: Mayursinh Sarvaiya <marvinduff97@gmail.com>

* chore(docs-ui): add docs for VSCode configuration eslint

Signed-off-by: Mayursinh Sarvaiya <marvinduff97@gmail.com>

* chore(ui): prettier set `trailingComma` to `none`

> prettier config default is changed after version bump - https://prettier.io/docs/en/options.html#trailing-commas

Signed-off-by: Mayursinh Sarvaiya <marvinduff97@gmail.com>

---------

Signed-off-by: Mayursinh Sarvaiya <marvinduff97@gmail.com>
2024-05-08 11:30:58 -04:00

441 B

Static Code Analysis

We use the following static code analysis tools:

  • golangci-lint and eslint for compile time linting
  • codecov.io - for code coverage
  • snyk.io - for image scanning
  • sonarcloud.io - for code scans and security alerts

These are at least run daily or on each pull request.