feature #1008 Be more specific in linting twig and yaml files (chr-he…

…rtel)

This PR was merged into the master branch.

Discussion
----------

Be more specific in linting twig and yaml files

I would argue that adding those parameters ensures linting that is more similar to the framework runtime in production:
symfony will parse tags in config yaml files and twig runtime might differ between dev and prod environment.

for example we would catch a forgotten `{{ dump() }}` in a twig template that way

Commits
-------

11bcecf Be more specific in linting twig and yaml files

.travis.yml

@@ -36,9 +36,9 @@ script:
   # this checks that the source code follows the Symfony Code Syntax rules
   - '[[ "$TRAVIS_PHP_VERSION" == "7.4snapshot" ]] || ./vendor/bin/php-cs-fixer fix --diff --dry-run -v'
   # this checks that the YAML config files contain no syntax errors
-  - ./bin/console lint:yaml config
+  - ./bin/console lint:yaml config --parse-tags
   # this checks that the Twig template files contain no syntax errors
-  - ./bin/console lint:twig templates
+  - ./bin/console lint:twig templates --env=prod
   # this checks that the XLIFF translations contain no syntax errors
   - ./bin/console lint:xliff translations
   # this checks that the application doesn't use dependencies with known security vulnerabilities