Skip to content

Conversation

@waralex
Copy link
Collaborator

@waralex waralex commented Oct 24, 2021

More accurate work with single Output. Fixes #84

Copy link
Contributor

@alexcjohnson alexcjohnson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💃 Looks great.

If you felt like being extra-paranoid with tests (but I don't think this is necessary for this PR) there are a couple more cases we could in principle cover:

  • Both in the single- and multi-output cases, have ALL match only a single element. Note this could be done by creating a new request to the same apps as in the new test and the one you just clarified the name, as we can assume the layout was changed as a result of some other callback.
  • A real multi-output callback, where one output is a regular string ID and the other one is an ALL that matches no elements at all, such that the callback should return an empty list for that second output. Note that if it's a single-output callback with just an ALL that matches no elements, the callback will never be triggered.

@waralex
Copy link
Collaborator Author

waralex commented Oct 25, 2021

If you felt like being extra-paranoid with tests (but I don't think this is necessary for this PR)

I created the #142 so as not to forget

@waralex waralex merged commit cb40b5a into dev Oct 25, 2021
@etpinard etpinard deleted the pattern_match_output_fix branch June 13, 2023 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Single Output with pattern match problem

3 participants