How about making configService available to RedisIoAdapter?

[db2crush]

Feature Request

How about making configService available to RedisIoAdapter?

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

import { IoAdapter } from '@nestjs/platform-socket.io';
import * as redisIoAdapter from 'socket.io-redis';
import { ConfigService } from '../config/config.service';

export class RedisIoAdapter extends IoAdapter {
**// now i am using like this line. But this is drawbacks because class is created newly.**
private configService: ConfigService = new ConfigService();

createIOServer(port: number, options?: any): any {
const server = super.createIOServer(port, options);
const redisAdapter = redisIoAdapter({
host: this.configService.getAsString(REDIS_HOST),
port: this.configService.getAsNumber(REDIS_PORT),
});
server.adapter(redisAdapter);
return server;
}
}

Teachability, Documentation, Adoption, Migration Strategy

How about inject adapter to module ???

What is the motivation / use case for changing the behavior?

[BrunnerLivio]

At some point you will instantiate the RediosIoAdapter class in your main.ts file.
You can simply get the ConfigService from the application context and and pass it over to the newly created RedisIoAdapter instance:

main.ts

const app = await NestFactory.create(ApplicationModule);
const configService = app.get(ConfigService)
app.useWebSocketAdapter(new RedisIoAdapter(app, configService));

redios-io.adapter.ts

export class RedisIoAdapter extends IoAdapter {
  constructor(app, private readonly configService: ConfigService) {
    // Or simply get the ConfigService in here, since you have the `app` instance anyway
    super(app);
  } 
  ...
}

You can read more about Application Context here.
Please let me know whether you found a solution using this approach. :)

[db2crush]

Missed the way of application context.
Nice approach. thx :)

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.