Inactivity Tracking Service requires Lavalink4NET logger (though it should be optional) about lavalink4net HOT 4 CLOSED

This gives me another question:
I add my ILogger to my provider by using .AddLogging(builder => builder.AddConsole()) (for testing etc.).

Then I register Lavalink-related stuff using:

.AddSingleton<IAudioService, LavalinkNode>()
.AddSingleton<IDiscordClientWrapper, DiscordClientWrapper>()
.AddSingleton(new LavalinkNodeOptions
{
    RestUri = "http://lavalink:8080/",
    WebSocketUri = "ws://lavalink:8080/",
    Password = "youshallnotpass",
    AllowResuming = false // (btw, I can pause/resume despite this setting)
})
.AddSingleton<InactivityTrackingOptions>() // This is new
.AddSingleton<InactivityTrackingService>() // This is new, too

So my question is: How do I get the logger to the LavalinkNode instance when using DI?

Offtopic:
By the way, good work on this library! I enjoy working with it.

from lavalink4net.

The problem is with Dependency Injection, for example when creating the instance of InactivityTrackingService using its constructor the issue is solved, I added to the 1.3.0-release milestone adding service provider constructors (or constructors without the optional parameters) for use with dependency injection.

As a "work-around" you could use the constructor of the InactivityTrackingService to avoid the ILogger as shown below:

new ServiceCollection()
    // [...] adding client wrapper, etc.
    .AddSingleton(sp => new InactivityTrackingService(sp.GetRequiredService<IAudioService>(),
        sp.GetRequiredService<IDiscordClientWrapper>(),
        sp.GetRequiredService<InactivityTrackingOptions>(),
        null))
    // [...]
    .BuildServiceProvider();

from lavalink4net.

This gives me another question:
I add my ILogger to my provider by using .AddLogging(builder => builder.AddConsole()) (for testing etc.).

Then I register Lavalink-related stuff using:

.AddSingleton<IAudioService, LavalinkNode>()
.AddSingleton<IDiscordClientWrapper, DiscordClientWrapper>()
.AddSingleton(new LavalinkNodeOptions
{
    RestUri = "http://lavalink:8080/",
    WebSocketUri = "ws://lavalink:8080/",
    Password = "youshallnotpass",
    AllowResuming = false // (btw, I can pause/resume despite this setting)
})
.AddSingleton<InactivityTrackingOptions>() // This is new
.AddSingleton<InactivityTrackingService>() // This is new, too

So my question is: How do I get the logger to the LavalinkNode instance when using DI?

Offtopic:
By the way, good work on this library! I enjoy working with it.

The ILogger-interface used by Lavalink4NET is not from Microsoft.Extensions.Logging(.Abstractions) anymore (since version 1.2.0, to remove the dependency).

See: https://github.com/angelobreuer/Lavalink4NET/blob/master/samples/Lavalink4NET.Discord_NET.ExampleBot/CustomLogger.cs for an example implementation of the interface. (It must be also added to the dependency injection service provider)

By the way:

AllowResuming = false // (btw, I can pause/resume despite this setting)

A note on this setting, this setting enables the session resume after reconnecting to the lavalink node to keep the player data (enqueued songs, etc.). Disabling the option will disconnect all players when stopping the bot.

from lavalink4net.

Hope the issue is fixed now with #8, release version 1.3.0 is now available (also on NuGet).

from lavalink4net.