You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A common use case for the lint commands (lint:yaml, lint:twig and lint:xliff) is to run them on CI.
While they report syntax errors currently, they don't allow failing when a deprecated feature is used (this is relevant at least for twig and yaml today). If would be great if they could have an option that would turn on reporting of any deprecation triggered as part of the parsing rather than only reporting parsing errors. This way, the CI can also prevent using deprecated Twig/YAML features.
The text was updated successfully, but these errors were encountered:
A common use case for the lint commands (
lint:yaml
,lint:twig
andlint:xliff
) is to run them on CI.While they report syntax errors currently, they don't allow failing when a deprecated feature is used (this is relevant at least for twig and yaml today). If would be great if they could have an option that would turn on reporting of any deprecation triggered as part of the parsing rather than only reporting parsing errors. This way, the CI can also prevent using deprecated Twig/YAML features.
The text was updated successfully, but these errors were encountered: