-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
37 IMessageFormatter and other fixes #38
Conversation
Update LoggerConfigurationTelegramExtensions.
ConfigAsMinimal(ExampleAppSettings.Token, ExampleAppSettings.ChatId); | ||
// ConfigAsMinimal(ExampleAppSettings.Token, ExampleAppSettings.ChatId); | ||
|
||
ConfigAsExtended(ExampleAppSettings.Token, ExampleAppSettings.ChatId); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe just an overload of Configure(...)
?
IMO, no sense to produce additional cognitive complexity for users
</ItemGroup> | ||
|
||
<ItemGroup> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can simply use a single ItemGroup
@@ -14,7 +14,7 @@ public static class LoggerConfigurationTelegramExtensions | |||
public static LoggerConfiguration Telegram( | |||
this LoggerSinkConfiguration loggerConfiguration, | |||
Action<TelegramSinkConfiguration> configureAction, | |||
IMessageFormatter messageFormatter, | |||
IMessageFormatter? messageFormatter, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing. That's an important fix as some users already had issues with that!
No description provided.