-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Issue: act allows ternary operator in expression #718
Comments
I'm not sure if this is a broader problem besides just the ternary operator. Github has some mini domain language for contexts/expressions, and I was not able to find documentation that describes if their expression DSL is a known language or not. I'm curious what |
I would say it's a broader problem
The ternary operator can be rewritten to Other examples
Not working with dtexpressions
... |
Interesting, I have not heard of this. A google search returns 0 results for "DTExpressions2". Any links? I'd be curious to read more.
I see. So perhaps a resolution of this issue could be documenting the discrepancy in the Known issues section of the README. |
DTExpressions2 is an internal azure pipelines product, which was (accidentally?) open sourced under the MIT License. Azure pipelines still uses version 1 of this language, I use this in my act clone for full compatibility with github. You could try this if you really need the same expression interpreter |
Issue is stale and will be closed in 14 days unless there is new activity |
This has been fixed with: #908 and will be released with the next version. |
Act version
Expected behaviour
act
shouldn't allow ternary operator syntax inside of an expressionReference: https://github.community/t/do-expressions-support-ternary-operators-to-change-their-returned-value/18114
Actual behaviour
act
does allow ternary operator syntax inside of an expression, and it fails when run as a github actionWorkflow and/or repository
workflow
Steps to reproduce
act
outputLog
The text was updated successfully, but these errors were encountered: