-
Notifications
You must be signed in to change notification settings - Fork 249
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
feat(logging): cloudwatch logging plugin to implement logging plugin interface #4107
feat(logging): cloudwatch logging plugin to implement logging plugin interface #4107
Conversation
} | ||
|
||
void _disableLogging() { | ||
_plugin.disable(); | ||
Amplify.Logging.enable(); |
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.
is this supposed to be Amplify.Logging.enable()
for the _disableLogging()
call?
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.
ops, I will fix it
- 'packages/smithy/smithy/lib/**/*.dart' | ||
- 'packages/smithy/smithy/pubspec.yaml' | ||
- 'packages/smithy/smithy_aws/lib/**/*.dart' | ||
- 'packages/smithy/smithy_aws/pubspec.yaml' |
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.
Are the smithy changes related?
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.
yes they are. they were added because of adding aws_logging_cloudwatch.
11d0d04
to
1fbc85e
Compare
93a2f8e
into
aws-amplify:feat/logging/cloudwatch
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.