-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Use either expr or govaluate consistently, not both #6823
Comments
I agree with this, but i don't know how we'd remove support without breaking users workflows. |
Are there any usages of govaluate other than |
I think a new |
@alexec I would like to work on it. Seems like a good first issue. Could you assign it to me? |
@denis-codefresh I think we (i.e. you) should create a new issue for |
Summary
Either
when:
should use antonmedv/expr ordepends:
and{{#
template tags should use Knetic/govaluate.There should be just one expression language/syntax be used consistently. Personally I'd be in favor of
expr
, but that matters less to me than to have a consistent developer experience.Use Cases
when:
,depends:
and{{#
expr template tags. Currently these use different expression syntax,when:
usesgovaluate
, whereasdepends:
and{{#
usesexpr
. This is confusing and not very maintainable.Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: