This repository has been archived by the owner on Jun 23, 2023. It is now read-only.
Adds options object, implements option implicitOptionalChaining, tests... #48
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.
I needed some functionality to evaluate expressions against an unknown context of query results. As such I have no guarantee that
results.foo
andresults.foo.bar
exist when I try to access them to determine whether my step will run. Catching thrown errors is not sufficient either, as an expression might evaluate against many results, which may or may-not exist, e.g.,results.foo.bar == true || results.baz.bar == true
.This PR adds an optional behavior to use an optional-chain when evaluating the object member expressions when the
implicitOptionalChaining
option is set to true. It also adds in support for options, and restructures the functions to do that in a more convenient way (similar to this PR #42).I also added some tests that validate the new behavior and ensure the old
throw
behavior still works.