feat: Define a Kitura.logTo() function for logging via swift-log #1460
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Depends on: Kitura/LoggerAPI#47
Convenience method of configuring Kitura to log to a swift-log logger, without requiring the user to depend on and import LoggerAPI.
Motivation and Context
LoggerAPI can now be configured to direct log messages to a swift-log Logger, instead of (or in addition to) a LoggerAPI backend (such as HeliumLogger).
Users who just want to use Kitura and swift-log would otherwise need to import LoggerAPI so that they can configure
Log.swiftLogger. This simplifies things by providing a simpleKitura.logTo()function which accepts a swift-logLogger.How Has This Been Tested?
Checklist: