commit 188eadc07b697a51c7049253a34bc4e9cda820cd
author Googler <noreply@google.com> Tue Feb 11 12:22:58 2020 -0800
committer Copybara-Service <copybara-worker@google.com> Tue Feb 11 12:23:52 2020 -0800
tree bfc396c31d09e3e5361655066c4534a4a7832223
parent 7f0ba75ae6da3ceca8e5e865a1ce9b8c71a5249e

Correct the instructions to generate an image of the dependency graph

Fix the path in the first occurrence to be under /tmp/ vs the current directory.
Change the output format from PNG to SVG (easier to browse and takes ~10 times less space).

PiperOrigin-RevId: 294494291

site/docs/query-how-to.html

diff --git a/site/docs/query-how-to.html b/site/docs/query-how-to.html
index a911ea5..acb5d06 100644
--- a/site/docs/query-how-to.html
+++ b/site/docs/query-how-to.html
@@ -130,9 +130,14 @@
 <p>To visualize the graph of all dependencies, pipe the bazel query output through
   the <code>dot</code> command-line tool:</p>
 <pre>
-$ bazel query "allpaths(//foo, third_party/...)" --notool_deps --output graph | dot -Tpng > graph.png
+$ bazel query "allpaths(//foo, third_party/...)" --notool_deps --output graph | dot -Tsvg > /tmp/deps.svg
 </pre>
 
+<p>
+  Note that <code>dot</code> supports other image formats, just replace <code>svg</code> with the
+  format identifier, for example, <code>png</code>.
+</p>
+
 <p>When a dependency graph is big and complicated, it can be helpful start with a single path:</p>
 
 <pre>
@@ -453,9 +458,9 @@
 
 <h4>What dependency paths do I have to break to make <code>bar</code> no longer depend on X?</h4>
 
-<p>To output the graph to a <code>png</code> file:</p>
+<p>To output the graph to a <code>svg</code> file:</p>
 
-<pre>bazel query 'allpaths(bar/...,X)' --output graph | dot -Tpng &gt; /tmp/dep.png</pre>
+<pre>bazel query 'allpaths(bar/...,X)' --output graph | dot -Tsvg &gt; /tmp/dep.svg</pre>
 
 <p><a name="Misc_"></a></p>