-
Notifications
You must be signed in to change notification settings - Fork 100
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
if
conditional marked as error if the YAML string is double quoted
#60
Comments
Noting that the workarounds also cause the conditional to not syntax-highlight anymore (a more minor annoyance to be sure, though). |
Another workaround which does preserve syntax highlighting is to wrap with - - if: "!startsWith(github.ref, 'refs/heads/release/')"
+ - if: (!startsWith(github.ref, 'refs/heads/release/')) |
* TAV-756: Add cutoff commit on new release branches * TAV-756: Add release commit just before tagging * Try to work around github/vscode-github-actions#60 again
Considering the lack of comments from any maintainers I am even wondering if we should assume this extension is abandonware, last release was like 9 months ago and an error like this is nowhere to be considered as a minor. @konradpabjan Maybe you can give this one a go, please? It is insane that this is apparently caused by not using a certified YAML parsers, as the double quotes are not expected to endup even being visible in the loaded data. |
Describe the bug
I have an
if
in my workflow that looks like this:The conditional is quoted because
!
has meaning in YAML to change the type, so we can't start a string with that character without a way to tell the YAML parser it's a string. This works fine in the workflow.However, it's marked as an error by this extension:
Workarounds that work
Workarounds that don't work
str
typingTo Reproduce
Use a double quoted condition.
Expected behavior
No error.
Screenshots

Extension Version
v0.25.3
The text was updated successfully, but these errors were encountered: