Incorrect type. Expected "string" when using a boolean value

Our YAML file begins as so:

trigger:
  batch: true
  branches:
    include:
      - master
  paths:
    exclude:
      - README.md

This extension complains about the usage of batch: true: Incorrect type. Expected “string”. The pipeline still works, and I worry that if I use "true" instead of true that it might be treated as a scalar value, in which case "false" will still evaluate to true.

Even the documentation shows an example of using the boolean value:

trigger:
  batch: true
  branches:
    include:
    - features/*
    exclude:
    - features/experimental/*
  paths:
    exclude:
    - README.md

This is similar to issue #283 which has the intellisense incorrectly complaining about another part of the yaml.

---

Extension Version: v1.170.0

Version: 1.46.1 (user setup) Commit: cd9ea6488829f560dc949a8b2fb789f3cdc05f5d Date: 2020-06-17T21:13:20.174Z Electron: 7.3.1 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: 7.8.279.23-electron.0 OS: Windows_NT x64 10.0.18363

[50Wliu]

Not that I know of, unfortunately. It actually seems to be auto-generated, meaning that it’s even harder to fix than I thought 😢.

[50Wliu]

Okay, did some more digging. I’m pretty sure that for tasks, the schema is auto-generated from each task’s task.json file. So if you’re seeing problems with an individual task’s validation, go submit a PR to https://github.com/microsoft/azure-pipelines-tasks. Still don’t know how the rest of it (i.e. trigger, etc) is generated though.