-
Notifications
You must be signed in to change notification settings - Fork 45
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
Deprecated annotations #121
Comments
The Application library will be removed completely in 2.0. Since Opulence follows semantic versioning, deprecated params will be removed in the next major release (2.0). |
I understand that, but you should give people more insight about what to expect. Without that, whoever wants to have an easy way upgrading to a future 2.0 can do absolutely nothing about these deprecations. |
There will be an upgrade guide. Still figuring out the full feature set for 2.0. |
I made my point, closing issue. |
Phan found a couple of issues related to code that is annotated as
@deprecated
.I'm thinking normally this check should just be disabled, because it's pretty common and normal for frameworks to mark methods which are deprecated as such. The reason I'm opening this issue is that I think
@deprecated
tags should give developers more information about what to expect. Like they should say with which version they will be removed and what developers should use instead. At the moment none of the tags seem to have this information and therefore they are confusing.The text was updated successfully, but these errors were encountered: