Remove DataLossAnalyzer and PerfAnalyzer #404
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
|
Hi @KamilSzostak, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
TTYL, MSBOT; |
Dmitry-Matveev
approved these changes
Feb 15, 2017
| // Uncomment if you want to use DataLossanalyzer | ||
| // new DataLossAnalyzerTests().registerTests(); |
There was a problem hiding this comment.
Is there a better way to disable DataLossAnalyzer rather then commenting it in 4 places? E.g. some configuration setting to only change one bit back and worth and avoid the case when someone forgets to uncomment/comment one of those.
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.
Comment out DataLossAnalyzer and remove PerfAnalyzer classes. Both functionalities are turned off and were designed for SDK internal use only.