mirror of
https://github.com/clap-rs/clap
synced 2024-12-14 14:52:33 +00:00
61c9e6265b
For those that want the original behavior, you can usxe `arg.help_heading(Some("FLAGS"))` on your flags. Limitations: - This will not give you a special sort order - This will not get a `[FLAGS]` added to usage For templates, we removed `{unified}` and `{flags}`. To help people catch these, a debug_assert was added. I'm unsure but I think there might be a change in behavior in calcuating when to show `[OPTION]` in usage. The old code only looked at `required` while flags looked only at arg groups. We now look at both. Ideally we'd add these in `_build` and remove special casing for no-groups except in the sort order of groups. I feel like thats best left for later. This also reduced the scope of `App`s public API. `get_*_with_no_heading` seemed a bit specialized to be in the public API. #2853 looks at splitting it out into its own PR. BREAKING CHANGE: Multiple - `UnifiedHelpMessage` removed - `{flags}` and `{unified}` are removed and will assert when present. - `get_*_with_no_heading` removed Fixes #2807 |
||
---|---|---|
.. | ||
ui | ||
app_name.rs | ||
arg_enum.rs | ||
argument_naming.rs | ||
arguments.rs | ||
author_version_about.rs | ||
basic.rs | ||
boxed.rs | ||
custom-string-parsers.rs | ||
default_value.rs | ||
deny-warnings.rs | ||
doc-comments-help.rs | ||
explicit_name_no_renaming.rs | ||
flags.rs | ||
flatten.rs | ||
issues.rs | ||
nested-subcommands.rs | ||
nested.rs | ||
non_literal_attributes.rs | ||
options.rs | ||
privacy.rs | ||
raw_bool_literal.rs | ||
raw_idents.rs | ||
rename_all_env.rs | ||
skip.rs | ||
special_types.rs | ||
subcommands.rs | ||
ui.rs | ||
utf8.rs | ||
utils.rs |