dearchap

@jtagcat We have support for persistent flags in v3 right now. So if you mark a flag as persistent it will be available to all subsequent sub commands. if sub...

@jtagcat Right now we have 2 competing arg parsers, yours and @meatballhat 's argh. At some point we have to make a decision which path is preferred.

I agree. We probably handle most of the use cases for a cli utility. Refitting a new parser is a nice engineering project but adds only incremental value

@abitrolly I agree with all of these points. In fact these have been raised before see https://github.com/urfave/cli/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Fv3 However at this point v2 is in maintenance mode so no new features/functionality....

Thanks @abitrolly

I have tried this on 2 different machines and gotten the same error. Is it something with a newer version of express or some other framework ?

@refs Yes we could implement this in v3. Are you willing to submit a PR ?

@refs Could you provide a description of the hooks you are looking for ?

Suggestion by user @axelrindle The concept of lifecycle hooks sounds great to me. I'd like to propose the following: - beforeFlags (runs before flags are parsed) - afterFlags (runs after...

@axelrindle we already have Before and After Actions for Command. I definitely see the value in Before & After Flags. The After Flags becomes tricky. When should it be called...