Consider using rich-click or typer

[antonymilne]

Alternative mentioned below: https://github.com/tiangolo/typer, which is based on click and uses rich if installed. Would be good to understand better what are the pros/cons of migrating and whether it would be worth the effort.

---

Originally written by @datajoely in #1464.

Warning. We need to consider whether this is actually a good change before implementing it. It would solve #1752 but should be discussed with @deepyaman and carefully tested to see if it's an improvement overall.

We could leverage the 3rd party rich-click package:

• The rich-click package is a small but actively maintained library which has reached v1.3.x at the time of writing.
• It is a drop-in replacement for click, all you have to do in theory is import rich_click as click
• If you want to use it piecemeal you can just provide the classes as arguments to the command/group decorators like I do here.
• The main benefit of this library is the fact we get much more readable help messages, like so:
  

[MatthiasRoels]

Why not use Typer instead? https://github.com/tiangolo/typer

[datajoely]

Good push - I was thinking the same this week!

[datajoely]

Here's how we'd migrate
https://typer.tiangolo.com/tutorial/using-click/

[antonymilne]

@MatthiasRoels: interesting thinking. I don't know whether it would be worth the effort migrating (e.g. there's some slightly weird custom stuff in our KedroCLI class), whereas changing to rich_click seemed to be a very simple change. But I would like to understand better how feasible this would be, the advantages, etc. I've added it to the ticket.

[astrojuanlu]

I think rather than pursuing Typer to solve #1752, we should make rich optional #2928 and keep Kedro as lean as possible (hence avoid adding yet another dependency).

[astrojuanlu]

We're proceeding with #2928