feature_request(validation): show all errors in the file `appveyor.yml`

[Kristinita]

1. Summary

It would be nice if AppVeyor will show all errors, not solely 1 error, when users validate the file appveyor.yml.

2. MCVE

2.1. appveyor.yml

build_script:
- node --version

image: Visual Studio 2022

install:
- choco install --yes nodejs

kira_goddess: true

kira_ideal: true

2.2. CLI command

HTTPie request:

https ci.appveyor.com/api/projects/validate-yaml @appveyor.yml --auth-type bearer --auth $MY_APPVEYOR_API_KEY --body

Or online validation on the page https://ci.appveyor.com/tools/validate-yaml.

3. Behavior

3.1. Current

AppVeyor shows solely one error. It doesn’t show that the key kira_ideal isn’t valid:

{
    "column": 1,
    "errorMessage": "Invalid setting or section: kira_goddess (Line: 9, Column: 1)",
    "isValid": false,
    "line": 9
}

3.2. Desired

Show all errors like Travis CI.

Command for validating the file .travis.yml with non-valid keys kira_goddess and kira_ideal:

https api.travis-ci.com/lint @.travis.yml Content-Type:"application/yaml" Travis-API-version:3 --body

Response:

{
    "@type": "lint",
    "warnings": [
        {
            "key": [],
            "message": "[warn] on root: unknown key \"kira_goddess\" (true)"
        },
        {
            "key": [],
            "message": "[warn] on root: unknown key \"kira_ideal\" (true)"
        }
    ]
}

4. Justification of the need of the feature

It’s standard default behavior for checkers/linters/validators. Almost all checkers/linters/validators that I know doesn’t exit after the first error they find, but continue to work. This behavior is more user-friendly. It’s more convenient for users to see all errors rather than every time running a validator after fixing one error.

Thanks.