#160 feat: add WaitForQuestion to ActiveWait #160
Closed
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.
Hey @jan-molak I've added
WaitForQuestion
in order to provide further waiting flexibility outside of waiting for an ElementFinder Condition to be met (which as I understand is focussed on a the state of a single element). In my project I found myself wanting to wait for more sophisticated conditions that lean on the parsing/transformation/aggregation that can only really be done in aQuestion
.So this pull request now allows you to do this kind of thing:
Wait.upTo(<duration>).untilQuestionAnsweredTrue(<boolean Promise returning Question>)