65 Commits (main)

Author	SHA1	Message	Date
Fabian Ruff	65d50017d4	search context hierachy for global flags	9 years ago
Ravi Gadde	bcec9b08c7	Added an API and test case for number of flags set	9 years ago
Jesse Howarth	a6bafbe9a5	Add additional test	10 years ago
Jesse Howarth	b490b5e35d	Add a function to determine if a global flag is set.	10 years ago
Ghislain Gt	98af61a59f	Add time.Duration flag type	10 years ago
Chris Winslett	c69522c960	Make Command accessible from Context	10 years ago
Yicheng Qin	5903a0a844	Add BoolTFlag type ... Compared to BoolFlag type, BoolTFlag treats 'true' as the default value for the flag. Without it, we have to use --no-action flag if we set the action is done in default. But sometimes it is bad to maintain flags with negative meanings. And it will be painful if we change the default value for the flag. As this implementation, it keeps all existing functionality. So it is compatible with old versions.	10 years ago
fraenkel	f88df0aa5a	Allow optional flags by asking if its been set/present on the command line	11 years ago
Jeremy Saenz	70eacca641	JMS #25: Added support for help flags	11 years ago
Jeremy Saenz	e14e45d087	More test tweaking	11 years ago
Jeremy Saenz	6664835bc1	JMS #14: Moving toward having and app object	11 years ago
Jeremy Saenz	59b0ce24ef	JMS #4: Support for global flags in cli.Context	11 years ago
Jeremy Saenz	3119b075d6	JMS #4: Flag testing	11 years ago
Jeremy Saenz	3f76896c4f	JMS #4: Getting some cli tests going. Testing out flags	11 years ago
Jeremy Saenz	6f22315082	JMS #4: Parsing command flags with context	11 years ago