-
Notifications
You must be signed in to change notification settings - Fork 320
Add back accidentally removed API #152
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
Conversation
Motivation: - When `source:` was added in apple#135, the API was accidentally broken despite source compatability. Modifications: - Add back source-less API calls which defer to the decls with source. - Note we can't deprecate the calls we're adding back: `log.info("some message")` refers to the implementation we're adding back rather and would therefore require users to explicitly specify a source to suppress the deprecation warning message. Result: - API is no longer broken.
a36d5cf
to
1815fd0
Compare
API breakages between 1.2.0 and 1.3.0:
|
API breakages between 1.2.0 and this PR:
|
I think these two are okay because of the default implementation on the
And this one is also fine for the same reason: it has a default implementation:
|
|
||
logging.history.assertExist(level: .error, message: "errorDescription") | ||
} | ||
} | ||
|
||
extension Logger { | ||
public func error(_ error: Error, | ||
public func error(error: Error, |
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.
fyi: I had to rename this so let error = logger.error(_:metadata:file:function:line:)
wasn't ambiguous
(Sorry for being slow to get to this, will do soon -- want to make sure it's really correct this time) |
No worries; I'm in no rush for this! |
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.
Oh my, I was pretty bad to follow up here but LGTM.
Going to release with this today
Motivation:
source:
was added in add source for log messages #135, the API was accidentally brokendespite source compatability.
Modifications:
log.info("some message")
refers to the implementation we're addingback rather and would therefore require users to explicitly specify a source
to suppress the deprecation warning message.
Result: