We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In one of our Azure pipeline files we have the following part:
publishDocs: - docsArtifact: 'doorstop-html' docsSubdirectory: '' ${{ if eq(parameters.debugrun, true) }}: docsName: '$(docsName)-test' ${{ else }}: docsName: '$(docsName)' docsDescription: '$(docsDescription)' ${{ if startsWith(variables['Build.SourceBranch'], 'refs/heads/release/') }}: excludeBuildNumber: true ${{ else }}: excludeBuildNumber: false
This causes a linter error at the last ${{ else }}: saying that "Map keys must be unique"
${{ else }}:
No linter error
Azure pipeline expressions seems to be parsed as map keys
See example in description
The text was updated successfully, but these errors were encountered:
This also occurs when using multiple ${{ inserts }} and other items that are preprocessed like:
${{ inserts }}
parameters: # pass along parameters ${{ insert }}: ${{ parameters }} ${{ insert }}: ${{ cfg }} # <-- Map keys must be unique error here
It would be awesome to have a setting for regex's for the linter to ignore.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
In one of our Azure pipeline files we have the following part:
This causes a linter error at the last
${{ else }}:
saying that "Map keys must be unique"Expected Behavior
No linter error
Current Behavior
Azure pipeline expressions seems to be parsed as map keys
Steps to Reproduce
See example in description
Environment
The text was updated successfully, but these errors were encountered: