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.

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

Trait or subclass to manage deprecations #20

Open
vreuter opened this issue Apr 19, 2019 · 1 comment
Open

Trait or subclass to manage deprecations #20

vreuter opened this issue Apr 19, 2019 · 1 comment
Labels
enhancement New feature or request priority-low

Comments

@vreuter
Copy link
Member

vreuter commented Apr 19, 2019

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.

@vreuter vreuter added enhancement New feature or request priority-low labels Apr 19, 2019
@vreuter vreuter mentioned this issue Apr 19, 2019
2 tasks
@nsheff
Copy link
Contributor

nsheff commented Apr 19, 2019

interesting thought. That does seem useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-low
Projects
None yet
Development

No branches or pull requests

2 participants