Configure OptimizelyLogLevel based on bundle type #1007
Merged
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
justinswart
approved these changes
Jan 2, 2020
Merged
ifbarrera
pushed a commit
that referenced
this pull request
Jan 8, 2020
* [NT-580, NT-702] Optimizely integration and Testable Client (#989) * wip - optimizely ab test set up * wip - optimizely struct * wip - optimizely * wip - optimizely refactor * wip - optimizely * wip - a testable optimizely client * wip - a testable optimizely client swift format * wip - optimixely refactor * wip - optimizely fix tests * wip - optimizely appdelegate test * wip - optimizely fix * wip - optimizely test environment * wip - optimizely * wip - remove func * [NT-580] Optimizely Integration Updates (#999) * Testing configuration result * Linking Optimizely with Framework instead of main app target * Updating targets * Cleaning up targets etc * Removing commented out line * Formatting * Remove test code * Line length * Add OptimizelyResultType with tests * Formatting and adding weak self * Line length * Chaining the variant enum into the guard Co-authored-by: Isabel Barrera <ifbarrera@me.com> * [NT-703] Pledge CTA A/B Experiment (#994) * wip - optimizely ab test set up * wip - optimizely struct * wip - optimizely * wip - optimizely refactor * wip - optimizely * wip - a testable optimizely client * wip - a testable optimizely client swift format * wip - optimixely refactor * wip - optimizely fix tests * wip - optimizely appdelegate test * wip - optimizely fix * wip - optimizely test environment * wip - optimizely * wip - remove func * See rewards experimental copy * wip - optimizely a/b experiment * snapshot testing * Formatting * Fixing targets, tests * Cleaning up warnings * Removing Optimizely imports * Specify control group in VC test * Merge * MockUUID and shared function * Formatting Co-authored-by: Isabel Barrera <ifbarrera@me.com> * Configure OptimizelyLogLevel based on bundle type (#1007) * Setting OptimizelyLogLevel based on bundle type * Formatting * Adding OptimizelyLogLevelType as a file Co-authored-by: Christella <cdolm92@gmail.com>
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.
📲 What
Configures the Optimizely SDK's log level based on the bundle type. For debug builds, the log level is
.debug, which gives us as much debugging information as possible. For release builds, the log level is set to.errorwhich is the highest possible log level, only logging severe errors.🤔 Why
To prevent excessive logging on release builds.
🛠 How
Added an additional output type
KSROptimizelyLogLevelto theconfigureOptimizelyoutput which will either be.debugor.errordepending on the main bundle type.♿️ Accessibility
N/A
🏎 Performance
N/A
✅ Acceptance criteria
[OPTIMIZELY] [DEBUG] SDK Version: 3.1.0🔮 Optimizely SDK Successfully Configured