You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And spit out the structs using a dot file encoder (hopefully there's something in the wild we can use, though it's not a super complex formatting)
But imho, the proposed insertion point and technique doesn't fit so well:
On one hand the existing awk script piggybacks query deps to rewrites the output, it is simple: the dependency graph is kept internally by please following a successful build, the translation is mechanical. This result is akin to Bazel. It could be added to please here,
On the other hand, the graph output of query graph is flat and embeds extra data (build state and more), inserting a dot output here would probably require to rebuild the dependency graph and, imo, poses at the very least the open question on how to represent the data. Addressing these questions seems to exceed the purpose of an encoder.
The question is: Should we add graphviz dot support now? If so, would it be acceptable to add it to query deps?
The text was updated successfully, but these errors were encountered:
izissise
added a commit
to Wuageorg/please
that referenced
this issue
May 26, 2023
Add an option --dot on query deps which
generate a dot compatible graph.
Graph nodes will have different shapes depending
if it's a filegroup/remote_file/text_file/binary
One can get an image with
`plz query deps //src:please --dot | dot -Tpng > graph.png`
issue thought-machine#2777
Add an option --dot on query deps which
generate a dot compatible graph.
Graph nodes will have different shapes depending
if it's a filegroup/remote_file/text_file/binary
One can get an image with
`plz query deps //src:please --dot | dot -Tpng > graph.png`
issue #2777
This issue originated on please gitter chan, it invites a discussion about adding
graphviz dot
support toplz
output:graphviz dot
formatawk
script that rewritesplz query deps <target>
output indot
But imho, the proposed insertion point and technique doesn't fit so well:
awk
script piggybacksquery deps
to rewrites the output, it is simple: the dependency graph is kept internally by please following a successful build, the translation is mechanical. This result is akin toBazel
. It could be added to please here,query graph
is flat and embeds extra data (build state and more), inserting adot
output here would probably require to rebuild the dependency graph and, imo, poses at the very least the open question on how to represent the data. Addressing these questions seems to exceed the purpose of an encoder.The question is: Should we add
graphviz dot
support now? If so, would it be acceptable to add it toquery deps
?The text was updated successfully, but these errors were encountered: