search

firecamp-io / firecamp

VSCode for APIs, Postman Alternative.
https://firecamp.dev
317 stars 22 forks source link

Websockets improvements #91

Closed iangregsondev closed 3 years ago

iangregsondev commented 4 years ago

Great tool!

I wonder if could make a suggestion, the listeners, maybe they should be an option to LISTEN automatically on connection and / or a button to say "Listen all"

Also ordering alphabetically the names of the listeners.

Also once connected I don't see a button to disconnect and / or reconnect - this would be really cool also.

It also would be really great if its possible to send down (sequentially) saved emitters.

For example, when I connect I have call 2 emitters, its mandatory. i.e.

image

Would be really cool if on a connect / reconnection - then it could call these 2 emitters that i saved.

also would be nice to have these events for listening / unlistening into its own panel

image

And finally, having all the websocket messages output to the main center works but after quite a few messages coming through - you kind of lose them.

It would also be nice to have an option to put them into another tab or something similar so you can separate and identify the events with the listeners and also filter on them

image

These are my ideas above and i am certainly not saying I am right but its what i found while working with it.

Great product - keep up the great work.

Thanks!

Nishchit14 commented 4 years ago

It'll definitely help us to design v2 for WS/SocketIO. Thanks for your suggestions @iangregsondev

evandroabukamel commented 4 years ago

Hello, everyone. I have a suggestion too. On the argument's value it would be good to have other types of parameters, like number and bool.

image

I'm testing a websocket and one on the parameters is expect to be a number but Firecamp sends a string, so it doesn't work. This websocket is created by an external JS package and I needed to change it's code to convert the string to number to make everything work. I opened an issue there, and I'm doing the same here. I believe that problem is not going to happen when we implement the client as we can send typed parameters, but in Firecamp I'm not able to send a number.

Thanks.

Nishchit14 commented 4 years ago

@evandroabukamel Your suggestion is truly remarkable. We'l surely implement it in v2 for WS and SocketIO.

Nishchit14 commented 3 years ago

Firecamp v2.0 released.