Skip to content
This repository has been archived by the owner on Jun 14, 2022. It is now read-only.

improve understanding of unmatched requests in interaction history #25

Open
aoberoi opened this issue Aug 22, 2017 · 1 comment
Open

improve understanding of unmatched requests in interaction history #25

aoberoi opened this issue Aug 22, 2017 · 1 comment
Labels
discussion M-T: An issue where more input is needed to reach a decision

Comments

@aoberoi
Copy link
Contributor

aoberoi commented Aug 22, 2017

current unmatched counts reflect interactions that are in the scenario but didn't get match anything that happened. what about things that happened that didn't match any interactions in the scenario?
@aoberoi aoberoi added question M-T: User needs support to use the project discussion M-T: An issue where more input is needed to reach a decision and removed question M-T: User needs support to use the project labels Aug 22, 2017
@lindycoder
Copy link

👍

I just started using this and when code is wrong, the python slack client just fails trying to parse JSON off the request because when the request is not matched, steno returns text/html and a 404.

Even catching this exception and calling /stop won't tell me what was expected and what was received.

Kind of hard to debug

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
discussion M-T: An issue where more input is needed to reach a decision
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aoberoi @lindycoder