workadventure/back/src/Model/Websocket/PointInterface.ts

import * as tg from "generic-type-guard";

/*export interface PointInterface {
    readonly x: number;
    readonly y: number;
    readonly direction: string;
    readonly moving: boolean;
}*/

export const isPointInterface = new tg.IsInterface()
    .withProperties({
        x: tg.isNumber,
        y: tg.isNumber,
        direction: tg.isString,
        moving: tg.isBoolean,
    })
    .get();
export type PointInterface = tg.GuardedType<typeof isPointInterface>;
Removing all "any" from back. To do this, I used generic-type-guard package which generates both an interface AND a valid type guard from code. With this, we are 100% sure that the messages we receive are validated at runtime! The client cannot pass us an object that is invalid! \o/ 2020-06-09 23:07:19 +02:00			`import * as tg from "generic-type-guard";`

			`/*export interface PointInterface {`
Refactored and optimized messages Now, when a user moves, only his/her position is sent back to the other users. The position of all users is not sent each time. The messages sent to the browser are now: - the list of all users as a return to the join_room event (you can send responses to events in socket.io) - a "join_room" event sent when a new user joins the room - a "user_moved" event when a user moved - a "user_left" event when a user left the room The GameScene tracks all these events and reacts accordingly. Also, I made a number of refactoring in the classes and removed the GameSceneInterface that was useless (it was implemented by the LogincScene for no reason at all) 2020-05-19 19:11:12 +02:00			`readonly x: number;`
			`readonly y: number;`
			`readonly direction: string;`
Removing all "any" from back. To do this, I used generic-type-guard package which generates both an interface AND a valid type guard from code. With this, we are 100% sure that the messages we receive are validated at runtime! The client cannot pass us an object that is invalid! \o/ 2020-06-09 23:07:19 +02:00			`readonly moving: boolean;`
			`}*/`

Applying Prettier on pusher and back 2021-06-24 10:09:10 +02:00			`export const isPointInterface = new tg.IsInterface()`
			`.withProperties({`
Removing all "any" from back. To do this, I used generic-type-guard package which generates both an interface AND a valid type guard from code. With this, we are 100% sure that the messages we receive are validated at runtime! The client cannot pass us an object that is invalid! \o/ 2020-06-09 23:07:19 +02:00			`x: tg.isNumber,`
			`y: tg.isNumber,`
			`direction: tg.isString,`
Applying Prettier on pusher and back 2021-06-24 10:09:10 +02:00			`moving: tg.isBoolean,`
			`})`
			`.get();`
Removing all "any" from back. To do this, I used generic-type-guard package which generates both an interface AND a valid type guard from code. With this, we are 100% sure that the messages we receive are validated at runtime! The client cannot pass us an object that is invalid! \o/ 2020-06-09 23:07:19 +02:00			`export type PointInterface = tg.GuardedType<typeof isPointInterface>;`