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

   For Airflow 3, we want a fully React UI. The first step is to create a new 
UI project at `airflow/ui`. 
   
   New tech:
   - vite
   Framework to build the react app
   - pnpm
   CLI command to install packages, handles dependencies better than yarn and 
npm
   
   Banner telling users to try the new UI:
   <img width="522" alt="Screenshot 2024-08-27 at 2 56 59 PM" 
src="https://github.com/user-attachments/assets/7bf7f947-9aba-4e69-b449-d9b1fd38975b";>
   
   New UI with the ability to go back to the old UI:
   <img width="1084" alt="Screenshot 2024-08-27 at 2 56 52 PM" 
src="https://github.com/user-attachments/assets/1fb7c846-c413-4534-96f5-c21759862965";>
   
   Hot reload works when running `breeze start-airflow --dev-mode` or 
manipulating the `dev_mode` env var and running the vite server manually.
   
   We could spend a lot more time improving precommit and breeze config. But 
I'd like to not get too bogged in that and get this project started.
   
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   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](https://github.com/apache/airflow/tree/main/newsfragments).
   


-- 
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