-
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
Fixed name of 20 remaining wrongly named operators. #8994
Fixed name of 20 remaining wrongly named operators. #8994
Conversation
3608aa6
to
e728743
Compare
I want to check other names as well. Give me 15 minutes. |
Could you look at the operators below?
|
I will fix those and build in protection |
Automated check during readme generation: Fixing it now:
|
dea47c1
to
8383ec9
Compare
Hey @kaxil @ashb @BasPH and @mik-laj -> I fixed the remaining 20 class names now. The CI tests will fail in the future in case somebody tries to commit a wrongly named class as well :).
Plus we will see in the CI job colorful output of what has changed in each of the packages (in case there are some changes) :). I fixed most of the tests and likely docs will be failing and need some fix - however @mik-laj -> maybe you can help. I see 14 tests failing in test_to_contrib and I am not sure where they are coming from - it all looks legit - I must have missed something. Can you help to fix it please? |
8383ec9
to
b9e3277
Compare
For docs, you should update this file: For the others, I'm waiting for the CI result. |
b9e3277
to
1a3247c
Compare
219d4d6
to
ed02e48
Compare
f309d67
to
366ea1c
Compare
366ea1c
to
beb9992
Compare
Hey @ashb -> the "parent" PR is now merged, so this one just contains the changes for "standardizing" all operator names. |
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.
Can't review for a few days, but don't let my review block any merge
So I dismiss your review so that i can merge it @ashb |
ash can't revoew it and we have 3 approvals already.
Make sure to mark the boxes below before creating PR: [x]
In case of fundamental code change, 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 UPDATING.md.
Read the Pull Request Guidelines for more information.