parsing will stop on the first invalid yml file.

• [x] remove note about not supporting multiple files from Readme

closes https://github.com/j13k/yaml-lint/issues/3

because of the re-indent of several lines at best review with whitespaces ignored: https://github.com/j13k/yaml-lint/pull/9/files?w=1

I've just created a git hook and I have to call the binary foreach file, I would prefer to call it with all files I want to check.

edit: I've seen that already does that, may I have a problem in my hook, but if I have multiples wrong yaml files, it only tells me what is wrong with one file

Good project, I was looking for a yaml linter I could install with composer

Hi there,

Could you tag a minor release with the 'name' field fix? Or just the latest master-commit? The latest tagged version is currently breaking builds in CI pipelines, unfortunately.

/ Yassin

Hi,

maybe we could add GPG signature to PHAR file in releases in order to make your PHAR file installable via phive tool.

Here is guide https://phar.io/howto/sign-and-upload-to-github.html

Added optional linter config via .yaml-lint.xml:

* <quiet> - true|false
* <includes> - Include paths, globs like src/*.yml are allowed
* <excludes> - Exclude paths, can exclude previous included path

Bumps symfony/yaml from 5.1.7 to 5.1.8.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Problem

As reported in feature request https://github.com/j13k/yaml-lint/issues/3 and https://github.com/lmc-eu/php-coding-standard/pull/8, there is an issue with glob style path specs (e.g. *.yml) not being handled correctly—only the last file in the set of filenames is parsed, but this is not clear in the output. This is confusing for users and could result in false reports.

Proposed Fix

Until the tool is upgraded to handle multiple files, it should be patched to reject glob style path specs and warn the user. The documentation should also clarify this.

Analysis

It seems $_SERVER['argv'] expands globs automatically, behaviour which was unexpected on my part. The script loops over the values of argv, assigning path values to a scalar argPath variable, which is then parsed. When multiple paths are specified (as in case of the expanded glob file set), the value of argPath ultimately rests on the last filename in the list.

This scratch script illustrates the issue using the Symfony Yaml component test fixture files as an example:

<?php print var_export($_SERVER['argv']) . PHP_EOL;

The script output demonstrates the implicit glob expansion:

$ php php-argv-test.php vendor/symfony/yaml/Tests/Fixtures/*.yml
array (
  0 => 'php-argv-test.php',
  1 => 'vendor/symfony/yaml/Tests/Fixtures/YtsAnchorAlias.yml',
  2 => 'vendor/symfony/yaml/Tests/Fixtures/YtsBasicTests.yml',
... lines deleted ...
  28 => 'vendor/symfony/yaml/Tests/Fixtures/sfTests.yml',
  29 => 'vendor/symfony/yaml/Tests/Fixtures/unindentedCollections.yml',
)

In the case of this path spec, only the last file, vendor/symfony/yaml/Tests/Fixtures/unindentedCollections.yml, is processed.

Hi! Can you please enable symfony 3.0 support for your library? As I can see, you are need to set version of symfony/yaml as ^2|^3 and it will be fixed.

The YAML component version is extracted from the installed.json manifest file created in vendor/composer on installation.

The format of this file seem to have changed, so the version is no longer extracted correctly.

Bumps symfony/yaml from 5.4.2 to 5.4.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps symfony/yaml from 5.4.0 to 5.4.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

We use this project to review YAML files and the intent is that linting should prevent any errors from malformed files, but we often get some errors on different sites when YAML files do not contain a trailing empty line, which isn't malformed. Can we separate out this error to a "strict" mode instead or maybe disable this check?

Currently an ugly error is thrown:

 ./bin/yaml-lint ~/foo/ 
PHP Notice:  file_get_contents(): read of 8192 bytes failed with errno=21 Is a directory in yaml-lint/src/yaml-lint.php on line 87

Description

Store linted filenames and signatures in a .gitignoreable results cache file, to allow unchanged files to be skipped.

Example

Cache filename: .yaml-lint-results-cache

Cache file contents:

/home/j13k/tests/test1.yml 9f57cb6838d2e1f2d0e0d9b1dacc36abe1946c61

Create unit tests to facilitate automated testing across PHP versions.

These can piggy back off the tests and fixtures in the main symfony/yaml module, but will need to capture and parse the console output instead.