Skip to content
New issue

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

azp: Stricter if else parser when using unrecognized contextes #327

Closed
ChristopherHX opened this issue Apr 30, 2024 · 1 comment · Fixed by #518
Closed

azp: Stricter if else parser when using unrecognized contextes #327

ChristopherHX opened this issue Apr 30, 2024 · 1 comment · Fixed by #518

Comments

@ChristopherHX
Copy link
Owner

The following passes on dev.azure.com, but fails here due to typo in parammeters

${{ if false }}:
  IsNull: ${{ replace(coalesce(parameters.y, parammeters.y), '''', '''''') }}

The following fails in both parsers

${{ if true }}:
  IsNull: ${{ replace(coalesce(parameters.y, parammeters.y), '''', '''''') }}
@ChristopherHX
Copy link
Owner Author

now new bug, the second failure doesn't had a test :(, now it succeeds.

Technically all suppressed errors should be added to a Warnings instance of TemplateValidationErrors, that can be enabled / disabled on demand

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant