AnalysisError `hasFix` attr (Implements #23874).

pkg/analysis_server/tool/spec/spec_input.html

Index: pkg/analysis_server/tool/spec/spec_input.html
diff --git a/pkg/analysis_server/tool/spec/spec_input.html b/pkg/analysis_server/tool/spec/spec_input.html
index 06de8fff576dbd11d6bac9a0e1d997342cf4d93c..b9e5ab3ef48364a8b67ad6e29e0eb34582d136e0 100644
--- a/pkg/analysis_server/tool/spec/spec_input.html
+++ b/pkg/analysis_server/tool/spec/spec_input.html
@@ -2027,6 +2027,13 @@
               message associated with the error code.
             </p>
           </field>
+          <field name="hasFix" optional="true">
+            <ref>bool</ref>
+            <p>
+              A hint to indicate to interested clients that this error has
+              an associated fix (or fixes).

[Brian Wilkerson, 2015/10/02 00:17:48]

This should make explicit that the absence of this field implies a value of
'false' (assuming that's true).

[scheglov, 2015/10/02 00:23:31]

I might worth to document that this flag may be "false negative", i.e. one or
more fixes may exist, but the flag is still "false" or missing.

[pquitslund, 2015/10/02 04:19:53]

Done.

[Brian Wilkerson, 2015/10/02 13:58:58]

Also, we should document whether or not we will ever produce a false positive
(saying that a fix exists when it doesn't). I think we should disallow that
case.

+            </p>
+          </field>
         </object>
       </type>
       <type name="AnalysisErrorFixes">