-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Description
Currently I'm providing structured config files alongside urfavecli, the problem with this is that config files for urfave are "just another way to declare flag values"; they are flat, not hyerarchical.
The workaround we're doing is ugly, as it goes against the defined priorities on urfavecli, since the only time I can set values on the flags are after these are already parsed (even the Before hook, flags have already been parsed by the time we reach it)
I've tried implementing the flag parsing myself but the prospects of maintaining this piece aside my usual work load is dark, and I haven't dig deep enough into urfavecli codebase to submit a patch, however I am willing to invest the time.
I guess I'm asking this because I've seen in some issues and comments that there is an active development for a v3, and perhaps this has been accounted for, perhaps not, or perhaps there is still room for feature submissions.
The reference point would be kong hooks, I have not personally used Kong, but these hooks seem to do just what we want.
This is the use case I'm trying to address: https://github.com/refs/urfave-yaml