dearchap
dearchap
Yes I've been dreaming up the idea of a "help personality". User can set the "help personality" to say ```ls``` or ```git``` style and the help output will match that...
@somebadcode can you send me the test code you are using for this ? I think it should be like this. ``` text := MockMarshaller{} cmd := &Command{ Name: "foo",...
@somebadcode I think the problem is you are trying to use the same instance for both Value and Destination. Generally this distinction is present when you have "simple" types ```...
@somebadcode I like that idea. Do you want include the FlagBase changes in this PR ? or should I make a separate PR for that ?
@somebadcode I started working on adding a new Destination Type and ran into some issues. I dont think its that trivial to add. I dont have cycles to spare this...
@somebadcode Thinking about this a bit more. Cant you achieve the same behavior using a GenericValueFlag ? Say you used ``` GenericFlag{ Name: "test", Destination: textValue(&slog.Logger{}) } ``` Would that...
@somebadcode Here is the test code I posted in the issue https://github.com/urfave/cli/issues/2051#issuecomment-2816482242
If you want to remove the GenericFlag templating of FlagBase and have both GenericFlag.Value and GenericFlag.Destination be set to cli.Value type it might be better suited for your use case...
@teghnet any reason you are not using v3 ? v2 is in maintenance mode
@tcard Which version of v2 were you upgrading from ? I dont think this behaviour has changed from v2 to v3. Alias "v" for "version" flag has been around since...