-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Add back missing [sources] link in generated documentation's includes
#49978
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
Conversation
|
I will have to regenerate the docs for airflow and providers released since the doc restructuring once this one is merged :) |
|
Hah. Turns out a numbef of examples will need to be moved |
oh.. can we patch some paths? |
10f2014 to
58f879e
Compare
|
No.. I really had to move a number of examples to "standar" provider - because they belonged there |
58f879e to
0aade65
Compare
|
Question. That change will lead to less number of example dags visible when Airflow starts with "load example dags"- becuase most of the example dags belong to "standard" provider now. But I think it's not necessary a bad thing - because IMHO we had far too many of those there. I'd say we should maybe (separately) make a small change when loading example dags will only load a subset of those, and maybe even load some from the standard provider? WDYT? This would be by far cleanest solution I think. |
Agreed |
0aade65 to
d2a3ab5
Compare
f9f7f14 to
1d0e0f3
Compare
7ea66b0 to
d58d66a
Compare
…ath (#50843) (#50877) The original PR #49978 that fixed generation of proper documentation for standard provider examples added retrieval of the path by checking import location for the standard provider. Instead we are now using direct path to the provider. (cherry picked from commit 13c6020) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…50843) The original PR apache#49978 that fixed generation of proper documentation for standard provider examples added retrieval of the path by checking import location for the standard provider. Instead we are now using direct path to the provider.
There were two issues with the test after migrating standard provider examples to ... standard provider (apache#49978) that made the test work only in Breeze and not in local env: * bad import of AIRFLOW_ROOT_PATH from scripts * reading system.standard import during parsing the pytest file Both issuses fixed here.
There was an issue with the test after migrating standard provider examples to ... standard provider (apache#49978) that made the test work only in Breeze and not in local env.
There were two issues with the test after migrating standard provider examples to ... standard provider (#49978) that made the test work only in Breeze and not in local env: * bad import of AIRFLOW_ROOT_PATH from scripts * reading system.standard import during parsing the pytest file Both issuses fixed here.
…50916) There were two issues with the test after migrating standard provider examples to ... standard provider (#49978) that made the test work only in Breeze and not in local env: * bad import of AIRFLOW_ROOT_PATH from scripts * reading system.standard import during parsing the pytest file Both issuses fixed here. (cherry picked from commit 396810d) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
There was an issue with the test after migrating standard provider examples to ... standard provider (apache#49978) that made the test work only in Breeze and not in local env.
…50916) (#50924) There were two issues with the test after migrating standard provider examples to ... standard provider (#49978) that made the test work only in Breeze and not in local env: * bad import of AIRFLOW_ROOT_PATH from scripts * reading system.standard import during parsing the pytest file Both issuses fixed here. (cherry picked from commit 396810d) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
There was an issue with the test after migrating standard provider examples to ... standard provider (apache#49978) that made the test work only in Breeze and not in local env.
There was an issue with the test after migrating standard provider examples to ... standard provider (apache#49978) that made the test work only in Breeze and not in local env.
…50843) The original PR apache#49978 that fixed generation of proper documentation for standard provider examples added retrieval of the path by checking import location for the standard provider. Instead we are now using direct path to the provider.
There were two issues with the test after migrating standard provider examples to ... standard provider (apache#49978) that made the test work only in Breeze and not in local env: * bad import of AIRFLOW_ROOT_PATH from scripts * reading system.standard import during parsing the pytest file Both issuses fixed here.
There was an issue with the test after migrating standard provider examples to ... standard provider (#49978) that made the test work only in Breeze and not in local env.
…ath (#50843) (#50877) The original PR #49978 that fixed generation of proper documentation for standard provider examples added retrieval of the path by checking import location for the standard provider. Instead we are now using direct path to the provider. (cherry picked from commit 13c6020) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…50916) (#50924) There were two issues with the test after migrating standard provider examples to ... standard provider (#49978) that made the test work only in Breeze and not in local env: * bad import of AIRFLOW_ROOT_PATH from scripts * reading system.standard import during parsing the pytest file Both issuses fixed here. (cherry picked from commit 396810d) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…50843) The original PR apache#49978 that fixed generation of proper documentation for standard provider examples added retrieval of the path by checking import location for the standard provider. Instead we are now using direct path to the provider.
There were two issues with the test after migrating standard provider examples to ... standard provider (apache#49978) that made the test work only in Breeze and not in local env: * bad import of AIRFLOW_ROOT_PATH from scripts * reading system.standard import during parsing the pytest file Both issuses fixed here.
) There was an issue with the test after migrating standard provider examples to ... standard provider (apache#49978) that made the test work only in Breeze and not in local env.
) There was an issue with the test after migrating standard provider examples to ... standard provider (apache#49978) that made the test work only in Breeze and not in local env.
The exampleinclude of ours used to have generated "sources" link to link to sources of the examples. This was however gone after recent doc build refactoring.
The problem was the example directive include import and lack of tests folder available on the python path. Both issues fixed in this PR.
Fixes: #49893
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.