check-azure-pipelines: doesn't handle default value for boolean parameter properly about check-jsonschema HOT 2 OPEN

The Azure Pipelines schema is provided by Microsoft and has numerous issues and inaccuracies.

I believe that their schema allows for "true" and "false" (the strings) in a number of cases in which "true", "false", true, false should all be allowed. I recommend trying "true" to see if Azure Pipelines and the schema are both happy with that.

I've tried to file upstream issues and even offered to help fix up their schema, and they either haven't understood me or haven't been interested in improving it. Their LSP tools simply patch over these cases by muddling the data before it goes through validation -- I can't remember the exact details, but it's nontrivial to replicate with the check-jsonschema technology stack.¹

I don't think that there's an obvious improvement here, unfortunately. It's a pretty disappointing but the underlying schema is where the problem lies.

It's possible that there's some kind of hack which can be applied (like the MSFT LSP tools do), but I haven't figured that out.

from check-jsonschema.