zilla
zilla copied to clipboard
k3po doesn't match beginEx before connected
Describe the bug k3po only matches the reply beginEx if the stream is in "connected" state. Even if we send it is misleadingly says that nothing arrived, as it only starts the matching process after connected.
To Reproduce Steps to reproduce the behavior:
- Create a test, where you're trying to match replyBeginEx on the client side
- In the implementation don't send reply window, so the stream is not yet in ":connected" state
- Run the test
- Check the diff saying, you haven't sent the reply begin
Expected behavior Even if we forget to send reply window (which is incorrect as the stream is not in "connected" state), k3po should match the replyBegin.