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

Using deprecated methods #43

Open
lars-seifert opened this issue May 31, 2018 · 1 comment
Open

Using deprecated methods #43

lars-seifert opened this issue May 31, 2018 · 1 comment
Labels
User Story This label should be used for user stories to distinguish them from "real" issues

Comments

@lars-seifert
Copy link
Contributor

Sometimes you call methods, that are deprecated, but are unaware of it. You can enable deprecation warnings, but they will only trigger if that path of code is executed.
We could check if the code does directly call a method that is marked as deprecated (which is not perfect, but does not require actually executing that path of code).
There is already a similar LinterTest, but it seems to be related to Pharao and I do not understand what it is actually doing. What are wellKnownClasses?
@lars-seifert lars-seifert added the User Story This label should be used for user stories to distinguish them from "real" issues label May 31, 2018
@sinnaj-r sinnaj-r mentioned this issue Aug 1, 2020
Closed
@LinqLover
Copy link
Contributor

When implemented, this should also consider methods that contain self flag: #deprecate instead of an actual deprecation. See [squeak-dev] The Inbox: 60Deprecated-nice.94.mcz for a current example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
User Story This label should be used for user stories to distinguish them from "real" issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lars-seifert @LinqLover