feat(exec): show container config in executable detail views#410
Merged
Conversation
Neither the markdown renderer (flow get) nor the TUI detail view (flow browse) surfaced a container block. Add a shared ContainerConfigMarkdown renderer in the types package and wire it into both shellExecMarkdown and shellExecConfig so image, runtime, mounts, volumes, user, network, and entrypoint are visible. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to the containerized-executions feature (#407): neither executable detail view surfaced the
container:config.flow get(markdown) —shellExecMarkdownrendereddir/logMode/cmd/filebut notcontainer.flow browse(TUI detail) —shellExecConfighad the same gap.Adds a shared
executable.ContainerConfigMarkdownrenderer and wires it into both paths, so image, runtime, workspace mount, volumes, user, network, and entrypoint are shown. Effective values are displayed, soSetDefaults-applied fields (runtimeauto, mount/workspace) are visible.Example rendered block:
Testing
ContainerConfigMarkdown(nil → empty; all fields present;entrypoint: ""→ "image default").Executable.Markdown()path includes the block.🤖 Generated with Claude Code