fix: removed info Optimizely logs #177
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
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #177 +/- ##
=======================================
Coverage 96.29% 96.29%
=======================================
Files 182 182
Lines 1699 1702 +3
Branches 300 300
=======================================
+ Hits 1636 1639 +3
Misses 58 58
Partials 5 5
☔ View full report in Codecov by Sentry. |
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
errorbefore creating the client, so only logs with a level oferrorare output to the console.This is because currently, all Optimizely logs are being output to the console, and 1 log in particular includes the currently logged in user's ID, which poses as a potential security issue
JIRA Ticket
PTECH-3307