-
Notifications
You must be signed in to change notification settings - Fork 36
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
Additional deprecations #685
Conversation
This reverts commit 102ef00.
Codecov Report
@@ Coverage Diff @@
## master #685 +/- ##
==========================================
+ Coverage 78.34% 78.39% +0.04%
==========================================
Files 66 66
Lines 7231 7256 +25
Branches 1586 1589 +3
==========================================
+ Hits 5665 5688 +23
- Misses 1251 1253 +2
Partials 315 315
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comments attached. Thanks so much for helping with this! This takes off a portion of the requires-1.x-deprecation
label. I'm not sure what's left. Maybe we should add the remaining ones to a milestone, or remove the label for the ones that are complete.
… and Job.workspace.
fddb95e
to
d4a347a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect! 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments but nothing that should block this PR based on our current pace and goal of gradual forward progress. Some review comments may warrant future work / may be worth tracking in an issue.
for more information, see https://pre-commit.ci
We'll discuss the cached property question at the next dev meeting then I think this PR is good to go. |
Description
This PR contains a number of deprecations as well as TODO comments indicated proposed deprecations. I have intentionally been a little bit aggressive with some of the proposals to spark discussion on whether certain APIs should continue to exist in the long term or not.
Motivation and Context
Aiming to slim down the API as much as possible in 2.0 as well as planning for future developments.
Types of Changes
1The change breaks (or has the potential to break) existing functionality.
Checklist:
If necessary: