-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Add doc page with providers deprecations #37075
Merged
mobuchowski
merged 1 commit into
apache:main
from
kacpermuda:feat/document-deprecated-classes
Feb 14, 2024
Merged
Add doc page with providers deprecations #37075
mobuchowski
merged 1 commit into
apache:main
from
kacpermuda:feat/document-deprecated-classes
Feb 14, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kacpermuda
force-pushed
the
feat/document-deprecated-classes
branch
from
January 29, 2024 17:33
bd56277
to
6682054
Compare
eladkal
reviewed
Jan 29, 2024
kacpermuda
force-pushed
the
feat/document-deprecated-classes
branch
2 times, most recently
from
February 2, 2024 09:33
4633f39
to
d91a047
Compare
kacpermuda
force-pushed
the
feat/document-deprecated-classes
branch
2 times, most recently
from
February 12, 2024 15:41
cecadb2
to
22dcf2f
Compare
potiuk
approved these changes
Feb 12, 2024
kacpermuda
force-pushed
the
feat/document-deprecated-classes
branch
2 times, most recently
from
February 12, 2024 17:24
1da0622
to
8d37005
Compare
eladkal
reviewed
Feb 12, 2024
eladkal
approved these changes
Feb 12, 2024
kacpermuda
force-pushed
the
feat/document-deprecated-classes
branch
3 times, most recently
from
February 14, 2024 07:57
cbff68d
to
1c50870
Compare
kacpermuda
force-pushed
the
feat/document-deprecated-classes
branch
from
February 14, 2024 12:14
1c50870
to
d483209
Compare
mobuchowski
approved these changes
Feb 14, 2024
Thank you @kacpermuda for this one! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TLDR
I want to add a documentation page that will have all the deprecated classes, methods, functions etc. It will get more information when #36876 is merged (where i switched all deprecations to decorators, so that i can detect them with static analysis).
Rationale
This is a step number 3 of the process described in #36876 , please refer to it for the rationale and in depth description.
Future possibilities
We can probably incorporate this information inside the actual class/method docs and not in separate page.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.