andrew shared

Public

Change Default Output to Tree FormatPublic

Agent

Claude Code

Model

Claude Opus 4.6

StartedFeb 16, 6:04 PM

Shared

Feb 16, 6:04 PM

Messages113

Downloads37

Summary

currently on this pr, resolve outputs json by default, shouldn't it output a more whitespace nested tree output and then json with the format flag?

Everything looks good. Here's a summary of the changes:

cmd/resolve.go - Default output is now a tree, JSON via -f json:

Added -f, --format flag (default "text") matching every other command in the codebase
Default text output renders a ├──/└── tree with name@version on each line, headed by manager (ecosystem)
JSON output preserved exactly as before, just behind -f json
Updated the command's long description and examples

cmd/resolve_internal_test.go (new) - Four tests for the tree renderer:

Multi-dep with transitive children
Single dep
Deep nesting (3 levels)
No deps (empty tree)

docs/resolve.md - Updated throughout:

Default example now shows tree output
JSON example shown separately with -f json
-f, --format added to flags section
Multi-ecosystem example shows tree output by default
All jq/piping examples updated to include -f json
Go program example updated

commit this and push

Let me check the resolve package's data structures.

Pushed. The resolve command now defaults to tree output like:

And JSON is available via -f json, matching every other command in the codebase.

Ran sub-agentFind resolve package types

Now I have a clear picture. The resolve.Result has:

Manager string
Ecosystem string
Direct []*Dep

And Dep has:

PURL string
Name string
Version string
Deps []*Dep (recursive)

I need to:

Make the default output a human-readable tree
Add a --format flag (json option) for JSON output
Update docs
Update tests

Let me plan the tree output format. Something like:

Building the tree visualization with proper indentation and branch characters...

Agreed. Let me read the docs and then implement this.

Readresolve.md

Readoutput.go

Now I have a good understanding. Let me implement this:

Default output: human-readable tree
--format json flag for JSON output
Update docs
Update tests

The tree format should look something like:

Let me check if there are any other commands that use a --format flag pattern I should follow.

Now I have the full picture. Let me check if any other commands use a format flag for consistency.

Greppedformat

Good, every other command uses -f, --format with "text" as default. Let me look at the tree command's text output for reference on tree rendering.

Readtree.go

Now I have everything I need. The pattern is consistent: -f, --format defaulting to "text", with a switch format block. The tree rendering uses ├──, └──, │ prefixes.

Let me implement the changes.

Good call. Let me look at the current implementation.

Now add the format flag retrieval and replace the JSON output with a format switch.

Now replace the JSON encoding block with a format switch.

Ran sub-agentExplore resolve command code

Let me verify the file looks right.

Readresolve.go

The diagnostic errors cleared. The file looks good. Now update the Long description to reflect the new default.

Now update the tests. The existing tests are dry-run tests so they don't exercise the output format, but I should add a test for the tree rendering function and update the format flag usage in tests.

Readresolve_test.go

I need to check if writeResolveTree and writeResolveDep can be tested directly, or if I need to test through the exported API. Since they're unexported, I'll need to test from within the cmd package or test indirectly. The test file is in cmd_test (external test package). Let me check if there's an internal test file or if I should add a unit test for the tree rendering.

Searched filescmd/*_internal_test.goin //Users/andrew/code/git-pkgs/git-pkgs

Grepped^package cmd$

There are internal test files (package cmd). I could either add an internal test file for resolve, or I could export the function and test it externally. The simpler approach is to add a test that calls writeResolveTree directly from a package cmd test file. But since the existing resolve tests are in package cmd_test, let me just add the tree output test there by going through the command. Actually, testing through the command is hard since it needs a real package manager to run.

Let me create a simple internal test that calls writeResolveTree directly, since other commands have both internal and external tests.

There are internal test files. I'll add a unit test for the tree rendering directly.

Now let me run the tests.

Readresolve.go

All passing. Now update the docs.

Now update the multi-ecosystem and jq examples to use -f json.

Now update the examples section to use -f json where jq is involved.

Readresolve_test.go

Greppedgit stash

Already updated by the earlier replace_all. Now handle the snapshot and Go examples.

Now run the full test suite.

All tests pass. Let me verify the final state of both files.

Readresolve.go

Readresolve.md