Simplifies communication over WebSocket.
-
Serialization/Deserialization out of the box
-
More structured way to exchange messages (separates
type
frompayload
)waitSocket.sendMessage('MESSAGE_TYPE', { somePayload: 'example' });
-
Convenient way to handle incoming messages:
waitSocket.onMessage('MESSAGE_TYPE', (payload) => doSomething(payload));
-
Ability to use a request/response paradigm with WebSockets (mechanism described below):
const { payload } = await waitSocket.sendRequest('MESSAGE_TYPE', requestPayload);
-
JSONSchema validation of each type of incoming and outgoing messages:
waitSocket.validation.incoming.addJSONSchema('MESSAGE_TYPE', jsonSchemaObject);
-
Ability to add interceptors to debug or modify incoming and outgoing messages:
waitSocket.interceptors.incoming.use((messageObject) => { console.log('Let\'s see what we have received', messageObject); // And modify the object return { ...messageObject, something: 'new', }; });
-
Flexible message format customization
-
Fully TypeScript
npm i waitsocket
or
yarn add waitsocket
import WaitSocket from 'waitsocket';
const waitSocket = new WaitSocket('ws://my.websocket.server:9000');
Or you can use it with your own instance of WebSocket, or even with some extensions like RobustWebSocket:
const ws = new RobustWebSocket('ws://my.websocket.server:9000');
const waitSocket = new WaitSocket(ws);
You can define JSONSchema for each type of your incoming and outgoing messages. For incoming messages, validation processes original deserialized message (before any interceptors). For outgoing messages, validation processes resulting message (after all interceptors, but before serialization, of course).
There is two ways of defining JSONSchema for messages: directly as a function argument when you send or receive a message, or link your JSONSchema to certain message type. You can combine these ways, for example, using type linking for outgoing messages (since you can send one message type in many places) and passing JSONSchema as a parameter to message handlers (since you probably handle one message type in one place).
It may seems excessive, to validate your own outgoing messages on a client side. But since it wouldn't cost you too much and there are still ways to corrupt your data (with interceptors or even with refactoring), I'm highly recommend you to validate both directions of your communication through WebSocket.
waitSocket.sendMessage('OUTGOING_MESSAGE_TYPE', payload, outgoingJSONSchemaObject);
waitSocket.sendRequest('OUTGOING_MESSAGE_TYPE', payload, null, outgoingJSONSchemaObject, incomingJSONSchemaObject);
waitSocket.onMessage('OUTGOING_MESSAGE_TYPE', (payload) => {...}, incomingJSONSchemaObject);
waitSocket.validation.incoming.addJSONSchema('INCOMING_MESSAGE_TYPE', incomingJSONSchemaObject);
waitSocket.validation.outgoing.addJSONSchema('OUTGOING_MESSAGE_TYPE', outgoingJSONSchemaObject);
If you wish to use your own message format, you can do it by extending WaitSocket class and overriding these functions, responsible for message construction and parsing:
getType(messageObject: MessageType): string
- Returns message type.getPayload(messageObject: MessageType): any
- Returns message payload.getRequestId(messageObject: MessageType): string
- Returns message requestId meta data.getMessageObject(type: string, payload?: any, requestId?: string): MessageType;
- Returns message object with type, payload and requestId in it.
Example (using body
parameter instead of payload
):
class myWaitSocket extends AbstractWaitSocket<MyMessageType> {
protected getMessageObject(type: string, payload?: any, requestId?: string) {
const result: DefaultMessageType = { type };
if (payload) {
result.body = payload;
}
if (requestId) {
result.meta = { requestId };
}
return result;
}
public getPayload(messageObject: PlainObject) {
return messageObject.body;
}
}