Set custom logger or overwrite verbosity option about click-extra HOT 4 CLOSED

Thanks @MLNW for considering my little project! 😃

click-extra is currently in an acceptable MVP state and good enough for me that I can share it between my 2 main projects (meta-package-manager and mail-deduplicate). Which means there's actually some hard-coded stuff, low documentation and lots of coupling that can be annoying. And I guess you stumble upon that.

I was hoping to iron things out depending on external interest. You're my first user, so yeah, sorry for the trouble! 😅

Do you have an example on how you are actually using the help screen colouring and configuration file loading? Does that work? I can reuse your examples as a base to improve the documentation. I only took the time to properly document the --config parameter.

Now I was planning at one point to use rich myself for logging. Can you show me how you'd like to use click-extra with rich?

from click-extra.

So far I simply replaced the @click.group with the @group annotation from click-extra.
That already colors the help screen and adds some additional options.
Configuring these options seems impossible though, which is the main issue I am having.

Before I had some simple logging configuration like this:

    logging.basicConfig(
        format=log_format,
        datefmt=date_format,
        style="{",
        handlers=[RichHandler(rich_tracebacks=True)],
    )

Now all other commands in my module would simply use the same logging configuration when using import logging.

from click-extra.

Defaults logger are now better supported and documented at: https://kdeldycke.github.io/click-extra/logging.html

(See #174 for more discussion on the topic).

from click-extra.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from click-extra.