as the given tsconfig.json does not have "strictNullChecks": true active, the result of your getSocket() was either the initialized this.socket object, or undefined. The return Type was still Socket, so TypeScript assumed a valid and initialized Socket object, what for instance broke my code.
This small fix inside the PR solves this issue by making the this.socket object either Socket | null.
Now it is possible in normal TS code to check for null and get an always working Socket object.
If this repo would turn on the strict mode of TS, the result would be lots of warnings 😺. May be a future project?
So, at least, nothing too fancy for now, but a fix for the kind of issues I had.
Possible Solution for #213:
as the given
tsconfig.jsondoes not have"strictNullChecks": trueactive, the result of yourgetSocket()was either the initializedthis.socketobject, orundefined. The return Type was stillSocket, so TypeScript assumed a valid and initialized Socket object, what for instance broke my code.This small fix inside the PR solves this issue by making the
this.socketobject eitherSocket | null.Now it is possible in normal TS code to check for
nulland get an always working Socket object.If this repo would turn on the strict mode of TS, the result would be lots of warnings 😺. May be a future project? So, at least, nothing too fancy for now, but a fix for the kind of issues I had.