brick VS typer

Thank you!

"stash", the initial MVP version, is written in Haskell. I chose Haskell mostly because of https://github.com/jtdaugherty/brick, which is a wonderful TUI library. I also tend to prefer functional programming languages when I have the choice.

However, Text 's backend and website are currently implemented in Clojure. The app is in C + Flutter (Dart).

Brick? Hadn’t heard of it so leaving for myself and others

Brick is a great library for terminal applications. I’d say start with the examples or take a look at some tutorials that use it, then just go at it.

Thanks. Yeah I was surprised myself at how much of a capable tool whiptail turned out to be. Especially since I'd heard it has issues with returning values, or not being as capable as dialog. I was actually in the midst of choosing between it, Haskell's brick, or python's PromptToolkit, yet settled on whiptail to see how far a bash approach could take me.

Written in Haskell with brick.

A declarative Unix terminal UI programming library written in Haskell (by jtdaugherty)

There is brick[1][2] for Haskell. Other languages may have something similar.

[1] https://hackage.haskell.org/package/brick

[2] https://github.com/jtdaugherty/brick/blob/master/docs/samtay...

In that vein, a declarative way to build (Text) UI like html+css. Or something along the lines of what Brick is for terminals.

I have been using Typer on every one of my CLI projects which uses Click under the hood. The documentation is fantastic, the CLI app it produces looks great and lets you create things quickly. I high recommend it.

https://typer.tiangolo.com/

Adding CLI capabilities. My preferred library here is typer.

I just heard about this but it seems to be pretty much the type of thing you want and want fast.

Docstrings are for documenting how a function/ class/ method/ module works. Often you don't need to add a docstring to your main function because no one will be importing it to use elsewhere. And if you want it to run as a CLI, then there are better ways to document the available options. For example, typer does most of it for you, or in click you add the help text to the decorator.

Most computing tasks in airflow DAGs are KubernetesPodOperator containing a CLI (Python Typer). It allows us to pass arguments easily to run DAG manually if needed (the new UI to pass arguments to DAG in airflow 2.6 is really nice). Arguments allow us to replay DAG easily (change start / end dates for instance).

So it's basically the main .gitlab-ci.yml file plus a separate Python CI app using Typer for the AWS instrumentation.

Similarly for Typer, which is literally "the FastAPI of CLIs"[1]. Handy to type your `main` parameters and have CLI argument parsing. For more complicated cases, it's a wrapper around Click.

[1] https://typer.tiangolo.com/

interesting that you hate python, but love Click. Did you try Typer which uses Click underneath?