This will be a game changer!

@bhagatparwinder I am curious, what type of behavior do you expect when mocking websockets? What would be the most useful for you?
Depending on the answer the implementation may be more or less complex.
It could be the same message (body) sent on each request, different messages depending on rules, etc
As a first step I would go for the simplest implementation, but it also needs to be useful.

I do agree with the simple approach first and build upon it later. A local socket that can provide the same body, to begin with. This would allow an application to load and a developer could work on part of the sites like UI and UX.

Eventually, if it could randomize the output each time using faker or chance that would be awesome!

@bhagatparwinder Thank you for your feedback 👍
Templating would be supported of course, so we could even be able to conditionally change the response message depending on the {{body}} helper using {{if}} or {{switch}}.

This would be great!

An advanced feature, for the future, could be the ability to send messages at some interval and/or by clicking a button in the Mockoon UI.

Thanks for the great software!

@doug2k1 it's on the roadmap for this year, but nothing has been decided yet. So if you have ideas concerning implementation or behavior of this feature they are welcome :)

@255kb is this still on the roadmap?

@trickpattyFH20 Yes it is. You can see the roadmap here and what I am currently working on. However, I cannot give any ETA. Among the tons of things I have to do on this project I would like to work on GraphQL or Websocket next, but these big features takes a lot of time!

I am expecting to do a PoC on websocket support. If everything goes smooth, I will be able to contribute with it.
Fingers crossed. 🤞