Currently, if an NSURLError is thrown from within the networking stack we do receive nice network task UI, but the description is largely difficult to read due to NetworkLogger.ResponseError just taking the raw debugDescription. It would be desirable to take the localizedDescription instead, as well as unwrapping the internal user info which could then be presented in the task UI.
For the general case, it would be best to allow NetworkLogger's configuration to take an (Error?) -> NetworkLogger.ResponseError closure that's called prior to sending the networkTaskCompleted event for user customizable ResponseError construction, as well as viewing this type's internal metadata in the task UI.
Currently, if an
NSURLErroris thrown from within the networking stack we do receive nice network task UI, but the description is largely difficult to read due toNetworkLogger.ResponseErrorjust taking the rawdebugDescription. It would be desirable to take thelocalizedDescriptioninstead, as well as unwrapping the internal user info which could then be presented in the task UI.For the general case, it would be best to allow
NetworkLogger's configuration to take an(Error?) -> NetworkLogger.ResponseErrorclosure that's called prior to sending thenetworkTaskCompletedevent for user customizableResponseErrorconstruction, as well as viewing this type's internal metadata in the task UI.