[BUG] Lack support for ACK callbacks

[derevnjuk]

Describe the bug

When using @Argsdecorators in the listeners from @tsed/socketio, the ACK callbacks are mistakenly passed to the deserialise function, which leads to a failure. The current implementation tries to deserialize callback functions when they are passed as arguments, which is not the appropriate behavior.

To Reproduce

1. Create a socket service with an input event that expects a callback function.
2. Define the callback function as an argument to the event.
3. Trigger the event and observe that the service attempts to deserialize the callback function, resulting in an error.

// server.ts
@SocketService("/room")
export class TestService {
  @Input("eventName")
  event(@Args(0) callback: () => void) { // throws an error
    callback();
  }
}

// client.ts
const socket = io("/room")
await socket.emitWithAck('eventName') // will never fulfilled 

Expected behavior

The callback function should be passed through without any attempt at deserialization.

Actual behavior

The callback function is incorrectly processed by the deserialization function, which results in a error

Repository URL example

No response

OS

macOs

Node version

Node v20

Library version

v7.67.8

Additional context

No response

[github-actions]

🎉 Are you happy?

If you appreciated the support, know that it is free and is carried out on personal time ;)

A support, even a little bit makes a difference for me and continues to bring you answers!

[Romakita]

🎉 This issue has been resolved in version 7.68.1 🎉

The release is available on:

• v7.68.1
• GitHub release

Your semantic-release bot 📦🚀