In a new post to the ServerGrove blog they look at linting tools for various circumstances including standard PHP, Twig templates and Composer configuration.
Today’s projects are built up from dozens of different components, configuration files, third-party libraries, tests, build scripts, etc. And even if you have the greatest test suite, bad things can happen sometimes. It’s important to catch bugs as early as possible, and syntax validators can be a great (and easy) addition to your continuous integration system. You would be surprised at how many problems are caused by syntax errors. At ServerGrove, we see these kind of problems with our clients almost every day.
Their list shows you how to lint (syntax check) several different types of content:
- standard PHP code
- Twig templates
- Composer configuration
- XML files
- Bash scripts
- JSON files
- YAML files
Some of them use tools that already come built-in (like PHP’s „-l“ or Twig’s „twig:lint“) but others require the use of external software such as xmllint or melody. Command examples are also included for each.