clap/tests
Ed Page 7515bfeb51 fix: Allow people to opt-in to deprecations
This adds a new `Cargo.toml` feature named `deprecated` that opts
controls whether deprecation warnings show up.  This is starting off as
non-default though that may change (see below).

Benefits
- Allows a staged rollout so a smaller subset of users see new
  deprecations and can report their experience with them before everyone
  sees them.  For example, this reduces the number of people who have to
  deal with #3822.
- This allows people to defer responding to each new batch of
  deprecations and instead do it at once.  This means we should
  reconsider #3616.

The one risk is people who don't follow blog posts and guides having a
harder time upgrading to the next breaking release without the warnings
on by default.  For these users, we reserve the right to make the
`deprecated` feature `default`.  This is most likely to happen in a
minor release that is released in conjunction with the next major
release (e.g. when releasing 4.0.0, we release a 3.3.0 that enables
deprecations by default).  By using a feature, users can still disable
this if they want.

Thanks @joshtriplett for the idea
2022-06-14 10:50:05 -05:00
..
builder test: Don't run legacy tests with v4 behavior 2022-06-13 16:47:25 -05:00
derive fix(derive): Switch default actions/parsers for unstable-v4 2022-06-13 18:59:58 -05:00
derive_ui fix: Allow people to opt-in to deprecations 2022-06-14 10:50:05 -05:00
ui test(output): Ensure correct streams 2022-04-22 10:56:47 -05:00
app.yml fix: Revert as much yaml policy to v2 as possible 2021-12-02 16:06:21 -06:00
derive_ui.rs test: Re-enable ui tests 2022-05-20 14:10:32 -05:00
examples.rs feat(multicall): Stablize multicall 2022-05-20 12:20:40 -05:00
macros.rs fix(parser): Deprecate ArgMatches::is_present 2022-06-10 14:21:25 -05:00
ui.rs feat(multicall): Stablize multicall 2022-05-20 12:20:40 -05:00
yaml.rs refactor: Update app variables to cmd 2022-02-14 15:55:56 -06:00