Task condition doesn't accept an expression

This is valid Pipelines YAML:

  steps:
  - task: UsePythonVersion@0
    condition: eq(variables.pypy, false)

But 143.0 gives red squigglies on the eq() part. One of the confusing features of Pipelines YAML is that condition fields can accept expressions that aren’t wrapped in $[] or ${{}}.

Since we don’t have syntax highlighting for expressions yet, the best we can do is accept a string for now.

[sk82jack]

I think I’ve run into this as well but not 100% sure so let me know if you want me to log a seperate issue.

I installed the extension and it told me my yaml was invalid because of an unexpected property jobs at the root level

If I remove the trigger and pr sections then the error changes to an incorrect type for the condition

So if I put the trigger and pr sections back in but change the condition to true then it validates the yaml OK.

[vtbassmatt]

Thanks @sk82jack - that looks like another example of this issue.