jscheffl opened a new pull request, #67390:
URL: https://github.com/apache/airflow/pull/67390

   As we have the Sphinx-Redoc issue with setuptools still not fixed and it 
seems the plugin is not maintained (see 
https://github.com/sphinx-contrib/redoc/pull/54) this PR attempts to replace it 
with swagger. As this is better maintained.
   
   DRAFT because:
   
   - Dark mode needs custom CSS, stay tuned
   - Net to check if CI really is good
   - Wait a moment for a feedback regarding the feature request in 
https://github.com/SAP/swagger-plugin-for-sphinx/issues/508
   
   What is does:
   
   - Remove redoc, allows to bump setuptools again!
   - Add swagger redenring from another lib (see 
https://pypi.org/project/swagger-plugin-for-sphinx/)
   - Adjust to mirror swagger code into the doctree for privacy
   - Adjust core, simple-auth-manager, fab and keycloak to new doc rendering
   - Add Edge REST API generation
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [ ] Yes (please specify the tool below)
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to