Skip to content

Trait or subclass to manage deprecations #20

@vreuter

Description

@vreuter

To facilitate accommodation for backward compatibility, there could be a subclass or trait for declaring deprecated keys/attributes and their newer versions, with an inferred default message that could be overridden. This comes up a decent amount within pepkit and would probably be more broadly useful, facilitating backcompat by abstracting away some of the handling of the deprecation thus lowering the cost of providing it.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions