Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(derive): Provide derive-friendly deprecation messages #3832

Merged
merged 5 commits into from Jun 14, 2022
Merged

fix(derive): Provide derive-friendly deprecation messages #3832

merged 5 commits into from Jun 14, 2022

Commits on Jun 14, 2022

  1. fix(derive): Reduce amount of deprecation noise 

    The main thing that might slip through is `bool`.  We'll see if we an
re-introduce that.
    @epage
    epage committed Jun 14, 2022
    Copy the full SHA
    89beb28 View commit details
    Browse the repository at this point in the history

  2. refactor(derive): Clarify the kinds of methods

    @epage
    epage committed Jun 14, 2022
    Copy the full SHA
    ce5cc92 View commit details
    Browse the repository at this point in the history

  3. refactor(derive): Split up chained calls

    @epage
    epage committed Jun 14, 2022
    Copy the full SHA
    ae81b09 View commit details
    Browse the repository at this point in the history

  4. fix(derive): Allow opting in to the original deprecations

    @epage
    epage committed Jun 14, 2022
    Copy the full SHA
    11fe3ce View commit details
    Browse the repository at this point in the history

  5. fix(derive): Provide derive-friendly deprecation messages 

    This is a step towards clap-rs#3822.  I'd say this fixes it but I'd want some
user acceptance before doing so.
    @epage
    epage committed Jun 14, 2022
    Copy the full SHA
    5881bd0 View commit details
    Browse the repository at this point in the history