Since Typer has a beautfiful terminal user interface (TUI), the README should include screenshots of terminal output instead of code blocks

[BlackSound1]

First Check

• I added a very descriptive title here.
• I used the GitHub search to find a similar question and didn't find it.
• I searched the Typer documentation, with the integrated search.
• I already searched in Google "How to X in Typer" and didn't find any information.
• I already read and followed all the tutorials in the docs and didn't find an answer.
• I already checked if it is not related to Typer but to Click.

Commit to Help

• I commit to help with one of those options 👆

Example Code

Run your application with the `typer` command:

<div class="termy">


// Run your application
$ typer main.py run

// You get a nice error, you are missing NAME
Usage: typer [PATH_OR_MODULE] run [OPTIONS] NAME
Try 'typer [PATH_OR_MODULE] run --help' for help.
╭─ Error ───────────────────────────────────────────╮
│ Missing argument 'NAME'.                          │
╰───────────────────────────────────────────────────╯
</div>

Description

Code blocks should generally be used either to have copyable code to paste elsewhere or to demonstrate code output. They should not be used to show rendered graphics (even if rendered to a terminal), that's for screenshots.

I propose that all instances of code blocks being used to show rendered Typer graphical output in the README should be replaced with actual screenshots.

Operating System

Linux, Windows, macOS, Other

Operating System Details

No response

Typer Version

ALL

Python Version

ALL

Additional Context

No response