Public

Change Default Output to Tree FormatPublic

The user wanted to change the default output of a command to show a nested tree structure instead of JSON, with JSON available only when specifically requested. The update was successfully made, including adding a format option, updating tests and documentation, and pushing the changes. The command now defaults to a readable tree format, with JSON output accessible via a format flag.

Agent

Claude Code

Model

Claude Opus 4.6

Shared

Feb 16, 6:04 PM

Messages113

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?

Good call. Let me look at the current implementation.

Let me check the resolve package's data structures.

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

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

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.

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.

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.

Let me verify the file looks right.

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.

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.

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

Now let me run the tests.

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.

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.

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

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

npm (npm)
├── express@4.18.2
│   ├── accepts@1.3.8
│   └── body-parser@1.20.1
└── lodash@4.17.21

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