Skip to content

[Tools] Linters

Vladyslav Yermolin edited this page Apr 15, 2024 · 2 revisions

We use the following tools to ensure needed code quality and smoothing of the processes:

  • Settings
  • Purpose - ensure proper names for the git branches. Possible prefixes:
  • task - working branches, from which the project will be deployed to gt-hub pages
  • hotfix - branches for quick fixes
  • setup - branches for setting up the project Examples of valid branches: task/01-about, setup/02-eslint
  • Settings
  • Purpose - ensure the same code settings for all editors: end of the line (lf), indentation (2 spaces), ...
  • Settings
  • Purpose - ensure the same code quality for js(x) and ts(x) files. All settings splitted into separate files in the folder ./eslint
  • Settings
  • Purpose - check all changed files, which are going to be committed by eslint and stylelint
  • Settings
  • Purpose - fix the node version on the project
  • Settings
  • Purpose - ensure the same visual appearance of the code
  • Settings
  • Purpose - ensure the same code quality for files of the styles