Linting
Automated checking of code for style and formatting errors according to fixed rules.
Linting refers to the automated checking of code by a tool, a so-called linter, that enforces fixed style and formatting rules – for example indentation, quotation marks, line length or the naming of variables. Well-known examples are ESLint for JavaScript, Pint for PHP or Ruff for Python.
Unlike static code analysis, linting is mostly not about runtime errors but about consistency: code from different hands should look the same, so that a diff shows only changes in substance and no formatting noise. Many linters correct violations automatically.
What Provimedia uses it for
Provimedia runs linters automatically before every commit so that formatting questions do not have to be negotiated in review.
Want to use Linting for your project?
In a free conversation, let's find out how we can implement this for you.
More from Software quality
Clean Code
Guiding idea for code that is designed to be understandable for humans and not just for the compiler.
Learn moreCode Review
Systematic examination of code by other developers before it is merged into the main branch.
Learn moreCode Smell
Conspicuous pattern in code that is not necessarily wrong but points to a deeper problem.
Learn moreDefinition of Done
Written list of criteria agreed in the team that a task must meet in order to count as done.
Learn moreMutation Testing
Technique that deliberately introduces small errors into the code to check how meaningful the tests are.
Learn moreQuality Gate
Check stage in the development pipeline that lets a change pass only if fixed criteria are met.
Learn moreRefactoring
Targeted restructuring of existing code without changing its external behavior.
Learn moreRegression Test
Re-testing of existing functions after a change in order to detect newly introduced errors.
Learn more