Make --include_aspect the default behavior for aquery.

From various user feedbacks, we've found that more often than not, aspect-generated actions should be included in the final result. RELNOTES: None PiperOrigin-RevId: 351315949
katre · Jan 12, 2021 · 44e46b8 · 44e46b8
1 parent 9d1c59b
commit 44e46b8
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/site/docs/aquery.html b/site/docs/aquery.html
@@ -155,7 +155,7 @@ <h4><code class='flag'>--include_artifacts, default=true</code></h4>
   Includes names of the action inputs and outputs in the output (potentially large).
 </p>
 
-<h4><code class='flag'>--include_aspects, default=false</code></h4>
+<h4><code class='flag'>--include_aspects, default=true</code></h4>
 
 <p>
   Whether to include Aspect-generated actions in the output.

diff --git a/src/main/java/com/google/devtools/build/lib/query2/common/CommonQueryOptions.java b/src/main/java/com/google/devtools/build/lib/query2/common/CommonQueryOptions.java
@@ -128,7 +128,7 @@ public String getLineTerminator() {
 
   @Option(
       name = "include_aspects",
-      defaultValue = "false",
+      defaultValue = "true",
       documentationCategory = OptionDocumentationCategory.QUERY,
       effectTags = {OptionEffectTag.TERMINAL_OUTPUT},
       help =