-
Notifications
You must be signed in to change notification settings - Fork 31
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
Discussion: Deprecation #154
Comments
Yeah that seems good. I would make the message a bit harsher, since many beginners do not know what "deprecated" means.
Also, not all changes might be as simple as "moved from one class to another", so we could also use a |
Good call @Qubus0. I've updated the methods to mention that. I've also added a version string to the args, with it being optional for the freeform method. |
Yep. This sounds exactly like what we need. 🚦🟢 |
Many of the changes outlined in #153 would be breaking, so for those, and for the future in general, it would be good to have a standardised way of handling deprecated method calls.
Suggestion
Example Usage
Keeping Old Files
If an entire class becomes deprecated, we can create a directory called
deprecated
and put that class there, with its contents just being all its old func definitions withdeprecated_changed
used for each one.The text was updated successfully, but these errors were encountered: