At the moment it's not as rich as all of the other command line libraries in term of types, enums etc but it's richer what it you can easily express with it.
For example, I challenge you do express logging configuration with oslo.config, or Click, org argparse.
You would be writing a whole lot of code to come up with something very rigid.
With Hydra composing hierarchical configs is trivial so logging configuration is not harder than anything else.
What you would do with those other CLI libraries is just is either either hard code your logging config (eew) or separate it into a different config file and add logic to deal with it. In my book this logic is an example of boilerplate that Hydra can handle cleanly.
At the moment it's not as rich as all of the other command line libraries in term of types, enums etc but it's richer what it you can easily express with it.
For example, I challenge you do express logging configuration with oslo.config, or Click, org argparse. You would be writing a whole lot of code to come up with something very rigid. With Hydra composing hierarchical configs is trivial so logging configuration is not harder than anything else.
What you would do with those other CLI libraries is just is either either hard code your logging config (eew) or separate it into a different config file and add logic to deal with it. In my book this logic is an example of boilerplate that Hydra can handle cleanly.