CP-1149 Use dartanalyzer fatal hints instead of post-processing on our own #108
Conversation
This file contains hidden or 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
Contributor
|
+1 😄 |
Member
|
+1 |
Contributor
|
+1 |
Current coverage is
|
jayudey-wf
changed the title
jayudey-wf
changed the title
Contributor
|
QA Resource Approval: +10
Merging into master. |
jayudey-wf
added a commit
that referenced
this pull request
Nov 25, 2015
CP-1149 Use dartanalyzer fatal hints instead of post-processing on our own
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Major facepalm here - dartanalyzer added support for fatal hints without me realizing it. So I am putting the analyze/api.dart back to how it was and adding the tag if fatalHints are enabled.
@evanweible-wf @maxwellpeterson-wf @trentgrover-wf