Firstly, Congrats on getting this functionality added! On a quick look, it seems pretty good.
Here are a few issues I’ve faced with it so far:
- I don’t seem to be able to name or save my requests, so can’t use them from within a collection.
- There doesn’t seem to be the option to use variables at any scope other than global in websockets. It would be nice to be able to define variables within the request scope - like regular http requests.
- I can’t remove or modify any of the headers (in particular, I wanted to be able to edit the “Sec-WebSocket-Extensions” header)
- (related to the 3rd point) I obtain a compressed response which doesn’t get decompressed before showing it to me, and doesn’t give me the option to decompress it.
- I think it would be more intuitive to be able to select previously sent messages under “compose”, rather than having to keep all messages sent and received and delve through them to decide which one to copy, copy it and head to the compose area to send.
- The pre-request and test scripts might be a good idea to include here as well. I’d like to be able to pull information out of messages received and use them for regular http requests.
In all, great work so far - being as ubiquitous as you are, you’re always likely to have very demanding users (like myself), but this should help you constantly improve and stay at your market leading position.