Lurgle.Logging v1.1.14 and Lurgle.Alerting v1.1.9 Released

MattMofDoom June 13th, 2021 22:59

I've pushed out updates to Lurgle.Logging and Lurgle.Alerting today.

The Lurgle.Logging update is minor - I noticed that Log.Add wasn't correctly passing the calling method, source file, and line number.

Lurgle.Alerting has received a more substantial update:

Alerting.IsDebug is a global boolean variable that is set via Alerting.SetDebug(). When set, it will ensure that recipients are automatically replaced with the debug email address. If you have a "debug mode" that can be switched on or off for your app, just make sure you set Alerting.IsDebug(true) for debug mode, configure MailDebug, and let Lurgle make sure you don't accidentally leak data while testing!
MailDebug is a new setting for the debug email address. This affords opportunity to differentiate a debug email address from your default MailTo address.
Comma- (or semi-colon) delimited email address strings will now always be consistently handled. If a delimited email address string is passed to one of the To(), Cc(), or Bcc() methods, it will automatically be parsed into the list of recipients.
Alert.From() and ReplyTo() also handle comma-delimited strings, but since these can only contain one email address - the first valid email address will be selected.
Invalid email addresses will automatically be filtered out
The Alerting.Init() method will automatically validate that the MailHost, MailFrom, MailTo, MailDebug, and MailSubject config values have been configured.
All Alerting.Init() failures are reported via the Alerting.AlertFailures static list, for handling via your code.