switch from govaluate to Expr (--filter <expr> option)
#99
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jandelgado
force-pushed
the
migrate_from_govaluate_to_expr_lang
branch
from
2b34905
to
9063b71
Compare
jandelgado
force-pushed
the
migrate_from_govaluate_to_expr_lang
branch
from
4aca5c6
to
baa3e42
Compare
Pull Request Test Coverage Report for Build 10479439162Details
💛 - Coveralls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
govalute not being maintained since 2017, this PR switches to Expr for use as the expression-evaluator of the
--filter <expr>option. The syntax ofExpris similar, but not the same, so this can be considered a breaking change.