Skip to content

Add response viewer to sendra-tui #114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dubemoyibe-star merged 1 commit into from
Sep 10, 2026
Merged

Add response viewer to sendra-tui #114

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

6 changes: 6 additions & 0 deletions sendra-tui/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,12 @@ clap = { workspace = true }
crossterm = "0.29.0"
ratatui = { version = "0.30.2", default-features = false, features = ["crossterm"] }
sendra-core = { path = "../sendra-core" }
# Pretty-prints a JSON response body in the response panel, the same
# `Content-Type` sniff and `to_string_pretty` sendra-cli's own
# `body_for_display` (`sendra-cli/src/output/human.rs`) uses, reimplemented
# here rather than shared because sendra-tui depends on sendra-core, not on
# sendra-cli.
serde_json = { workspace = true }
# Drives the request execution pipeline (`sendra_core::send`, which reqwest
# needs a runtime under). Current-thread only ("rt"): each run spins up its
# own runtime on its own OS thread (see `run_request::spawn`) rather than
Expand Down
Loading