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.
Issue #, if available:
https://github.com/aws-amplify/aws-appsync-realtime-client-ios/issues/31
Description of changes:
Allow the logging level to be configurable allows the consumers of this package (API Plugin and AppSync SDK) to set it through its log level. In Amplify, when the developer sets
Amplify.Logging.logLevel
, this can be propagated toAppSyncRealTimeClient.logLevel
when the plugins are configured. Since the intention is to propagate the log levels from Amplify, they are identical to the ones defined in Amplify.Logging category https://github.com/aws-amplify/amplify-ios/blob/main/Amplify/Categories/Logging/LogLevel.swiftAppSyncRealTimeClient.logLevel = .verbose
by developers after callingAmplify.configure
if they are debugging and want the logLevels to be different from Amplify.Logging's logLevel, though i don't think this is a very common use case, as developers should just be operating onAmplify.Logging.logLevel
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.