Linter
A tool that examines code for particular problems using configured rules.
What is a linter?
A linter examines code using configured rules. These may address possible errors, agreed code conventions or style. The language, files and patterns checked depend on the tool and configuration. Linting is therefore not limited to indentation, but it is not a complete check of application behaviour either.
In a fictional portal project, an enabled rule might flag an unused variable in the request module. The team checks whether to remove it or whether it points to a forgotten processing step. Some findings can be fixed automatically; others require a decision. Changes need to remain traceable. A clean lint run establishes only the rules performed on included files; tests and business-focused code review remain complementary tasks.
Sources
Related terms
- Static code analysisExamining code, or a representation of it, without running the application’s workflows to do so.
- Typing in programmingHow a programming language handles kinds of values and suitable operations.
- Code reviewFocused examination of a source change for design, behaviour, clarity and appropriate checks.
- Unit testA focused check of a small, defined part of software, such as a rule or function.
- Contract testA test of agreed messages between a consumer and a provider at an application interface.
- Test coverageThe share of an explicitly defined set, such as executable statements or requirements, that has been tested.
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.