v3.0.1

What's new

• Minor bug fixes and improvements
• Assertion failures are now triggered from its own destination, by default disabled
• File, line, and function parameters now use correct types
• Removes assertion failures from the console destination (fixed in 3.0.1)

2.0 to 3.0 Migration guide

1. Remove the minimumLevelForAssertionFailures setting from your console destination settings (if you have it). If you still want assertion failures, you need to now add the assertion failure destination - optionally with any custom settings you desire:

        MELoggerDestinationManager.shared.add(
            AssertionFailureDestination(
                settings: .init(isEnabled: true, minimumLevel: .error)
            )
        )

2. You'll have to convert your custom destinations like so:

    /// Old logging function, uses String and Int for file line and function
    public func log(
        ...
        file: String,
        line: Int,
        function: String
    ) 

    /// New one uses StaticString and UInt
    public func log(
        ...
        file: StaticString,
        line: UInt,
        function: StaticString
    )