[BUG]: trigger and stages are marked as invalid in a .yml file

[BigHoss]

Describe the bug valid yml content is marked as invalid

To Reproduce Steps to reproduce the behavior:

1. create an azure-pipelines.yml
2. content:

   
   trigger:
   - main
   pool:
   vmImage: ubuntu-latest

variables: buildPlatform: 'Any CPU' buildConfiguration: 'Release' disable.coverage.autogenerate: 'true'

stages:

• stage: build displayName: Build Project

  jobs:

  • job: init displayName: Initialize the Build steps:

    • task: UseDotNet@2 inputs: version: '8.x' displayName: 'Install .NET 8'

  • job: build-api displayName: Build the api variables: projectFile: './src/Api/Api.csproj' sonarQubeProjectName: 'Api' steps:

    • template: build-steps.yaml

  • job: build-webui displayName: Build the WebUi variables: projectFile: './src/Client/Client.csproj' sonarQubeProjectName: 'Client' steps:

    • template: build-steps.yaml

  • job: build-tests displayName: Build the tests variables: projectFile: './src/Tests/*.csproj'
    steps:

    • template: build-steps.yaml

  • job: run-tests displayName: run tests variables: projectFile: './src/Tests/*.csproj'

Expected behavior code completion

Screenshots

Desktop (please complete the following information):

• OS: Win11
• Browser none
• Version 2024.1.24

JetBrains IDE (please complete the following information):

• IDE: Rider
• Version: 2023.3.3 (#RD-233.14015.60)

Azure Devops organization details:

• 2 devs

[Jonatha1983]

Hi @BigHoss thanks for reporting.

I saw this issue and it is due the bad json schema provided by Microsoft.

I amusing the same one they use for vscode and I am periodically checking for updates hopefully they will fix those issues.

I ll mark this issue with both bug and block labels and I will update once there is a new fixed version.

You can turn off the inspection in the AZD settings if this is really bothering you.

Thanks again for reporting

[Jonatha1983]

Hi @BigHoss, I found a way to fix it - you can disable the depreciation warnings for this specific inspection in the settings.

This is a workaround. I am consulting with Jetbrains on how to do that in the code.

Closing this issue for now will update once a version with a fix is released.